Re: failing build 4.5.2: execvp: /bin/sh: Argument list too long

["Kevin P. Fleming" <kpfleming at digium dot com>]

On 12/28/2010 06:19 AM, Oliver Kullmann wrote:
> Hello,
>
> building gcc version 4.5.2 (with C, C++, Fortran) I get the build error
>
> libtool: compile:  /home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/builds/Gcc/gcc-4.5.2_build/./gcc/gfortran -B/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/builds/Gcc/gcc-4.5.2_build/./gcc/ -B/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/Installations/Gcc/4.5.2/x86_64-unknown-linux-gnu/bin/ -B/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/Installations/Gcc/4.5.2/x86_64-unknown-linux-gnu/lib/ -isystem /home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/Installations/Gcc/4.5.2/x86_64-unknown-linux-gnu/include -isystem /home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/Installations/Gcc/4.5.2/x86_64-unknown-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/builds/Gcc/gcc-4.5.2/libgfortran -iquote/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/builds/Gcc/gcc-4.5.2/libgfortran/io -I/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/builds/Gcc/gcc-4.5.2/
libgfortran/../gcc -I/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/builds/Gcc/gcc-4.5.2/libgfortran/../gcc/config -I../.././gcc -D_GNU_SOURCE -I . -Wall -Werror -fimplicit-none -fno-repack-arrays -fno-underscoring -fallow-leading-underscore -g -O2 -c /home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/builds/Gcc/gcc-4.5.2/libgfortran/intrinsics/f2c_specifics.F90 -o f2c_specifics.o>/dev/null 2>&1
> /bin/sh ./libtool --tag=CC   --mode=link /home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/builds/Gcc/gcc-4.5.2_build/./gcc/xgcc -B/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/builds/Gcc/gcc-4.5.2_build/./gcc/ -B/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/Installations/Gcc/4.5.2/x86_64-unknown-linux-gnu/bin/ -B/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/Installations/Gcc/4.5.2/x86_64-unknown-linux-gnu/lib/ -isystem /home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/Installations/Gcc/4.5.2/x86_64-unknown-linux-gnu/include -isystem /home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/Installations/Gcc/4.5.2/x86_64-unknown-linux-gnu/sys-include    -std=gnu99 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wextra -Wwrite-strings -fcx-fortran-rules -ffunction-sections -fdata-sections  -g -O2   -o libgfortran.la -version-info `grep -v '^#' /home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/
builds/Gcc/gcc-4.5.2/libgfortran/libtool-version`  -no-undefined -bindir "/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/Installations/Gcc/4.5.2/bin" -lm  -Wl,--version-script=/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/builds/Gcc/gcc-4.5.2/libgfortran/gfortran.map -rpath /home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/Installations/Gcc/4.5.2/lib/../lib64 backtrace.lo bounds.lo compile_options.lo convert_char.lo environ.lo error.lo fpu.lo main.lo memory.lo pause.lo stop.lo string.lo select.lo all_l1.lo all_l2.lo all_l4.lo all_l8.lo all_l16.lo any_l1.lo any_l2.lo any_l4.lo XXX many more of these XXX
> make[4]: execvp: /bin/sh: Argument list too long
> make[4]: *** [libgfortran.la] Error 127
> make[4]: Leaving directory `/home/csoliver/SAT-Algorithmen/OKplatform/ExternalSources/builds/Gcc/gcc-4.5.2_build/x86_64-unknown-linux-gnu/libgfortran'
>
> I know that with newer Linux versions longer command lines are possible.
> However I wonder whether I really have to upgrade my operating system (right now)?
>
> I'm running bash in a recent version
>
> > /bin/sh --version
> GNU bash, version 3.2.48(1)-release (x86_64-unknown-linux-gnu)
> Copyright (C) 2007 Free Software Foundation, Inc.
>
> Also binutils are up-to-date.
>
> But this doesn't help. Is there some flag? xargs-usage in the makefiles would also apparently solve
> the problem.
>
> I'll try it now with cleaned environment (perhaps I'm lucky). Sooner or later I have to upgrade the operating system,
> but right now it would be good of there would be some other method (deadlines are waiting).

If you built in a shorter directory path (which is repeated quite a few 
times in the command lines you posted) the total command line length 
would be shorter.

--
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kfleming@digium.com
Check us out at www.digium.com & www.asterisk.org