Hi All,

Im facing compilation problem.
The compilation gives an error of "too many arguments" since there seem to be an OS limitation of command length in all the new OS versions. The compilation is kernel dependent and is not compatible with my 2.6.9-67.

I have an old machine which has an kernel version(2.4.21), i am using this machine for Compilation.

execvp: /bin/sh: Argument list too long - This is a common problem which actually signifies limitation of OS, and exists for solaris and other distros also.
--------------
Error that comes in all other kernel versions except 2.4.21-40:-
------------
gmake[1]: Entering directory gmake[1]: execvp: /bin/sh: Argument list too long
gmake[1]: *** Error 127
gmake[1]: Leaving directory
-----------

Can you please suggest some solution for this. If something can be done with the code, which can solve this problem , or if some patch is available to fix this.


Link for workaround on similar Lines :-
http://kbase.redhat.com/faq/docs/DOC-2504


Many thanks in advance.

Cheers
Sahil

Actual limitation is not on command length, but on command length + environment length.

So if you clean some of your environment variable it may help

Hi,

Like you said, Actual limitation is not on command length, but on command length + environment length , the default space is 131K , which equals 128K argument and enviornment 3K , which is defined in limits.h.

Can you suggest some work around, how to clean the environment variables to fix this as i tried doing the clean using gmake clean before starting the compilation...!!!

You can try

http://kbase.redhat.com/faq/docs/DOC-2504

Just checked this post. Find it Useful on similar lines..!!

You don't indicate what program you are trying to build.

Some programs (like newlib or glibc) generate long argument lists to add object files to archives. The makefile can be edited to covert a single invocation of a program (say, ar) to use xargs.

I tried but not work...........

You have re-opened a thread that had been closed for **ELEVEN YEARS**...not surprised at all that the advice in here doesn't work now. And if you want help you need to go back to your OTHER thread about the same issue.