Re: [microblaze-uclinux] Build error - microblaze-uclinux-ar: Argument list too long

[Frank Lombardo <flombardo@xxxxxxxxxxxxx>]

----- Original Message ----
> From: John Williams <jwilliams@xxxxxxxxxxxxxx>
> To: microblaze-uclinux@xxxxxxxxxxxxxx
> Sent: Thursday, July 10, 2008 8:08:48 PM
> Subject: Re: [microblaze-uclinux] Build error - microblaze-uclinux-ar: Argument list too long
> 
> Hi Frank,
> 
> Frank Lombardo wrote:
> > After adding a second MPMC to a design, we are getting the following 
> > error while building the software.  I have tried to identify the 
> > difference between the two projects, but don't see anything that should 
> > cause the error.  The argument list in question is long, but it is 
> > exactly the same as the working single MPMC version.  Can anybody shed 
> > some light on this situation?
> 
> That's very strange.  THe only thing I can think of is that, due to the 
> way we export *every* EDK/MHS releated parameter to the kernels .config 
> space, which in term enters the environment variable space of the 
> Makefiles that run, perhaps the addition of this extra MPMC has pushed 
> that environment space past the limit.
> 
> I know the reported error is "Argument list too long", but masybe this 
> is a misstatement of the real error that would be something like "out of 
> environment space".
> 
> Something you might like to try as a workaround, is delete all of the 
> parameters associated with the MPMCs from the Kconfig.auto file in your 
> arc/hmicroblaze/platform/XXX-YYY directory, and rebuild the whole thing. 
>   The MPMC-related params aren't used in the build, it's just the 
> main_memory_start and _size that Linux cares about.
> 


John,

I had done some additional testing, and the results agree with what 
you describe.  I was able to get the build to succeed by commenting 
out a large set of the unused MPMC parameters.  

One curious thing that I noticed is that I could get the project to build
by moving the petalogix directory closer to the root.  I assume the path
must end up in environment variable space as well.  Shortening the path
must have freed up enough space to let the build work.

I'm happy with the workaround, but can you think of a way to automate
reducing the number of unneeded parameters in the Kconfig.auto file?

Thanks for all the help you have given me.

Frank

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/