LFS Version SVN-20060501 - GCC-4.0.3 - compilation fails

Dan Nicholson dbn.lists at gmail.com
Wed May 17 16:05:09 PDT 2006

On 5/17/06, Mag. Leonhard Landrock <1977-Hamlet at gmx.at> wrote:
> First of all: Thank you for so much care.

No problem.  I'd like to figure out what the issue is.  Especially
since someone else is stuck at the same spot.

> > This might be a dead end I'm leading you down, but could you find the
> > part in the build log where cppdefault.o is compiled?
> I'm not sure wehter I did it the right way. I did the following to get the
> build log:
> make > GCC.LOG | >> GCC.LOG | >> GCC.LOG | >> GCC.LOG | >> GCC.LOG | >>

Normally, what you want is this:

make 2>&1 | tee GCC.LOG

Then 2>&1 redirects stderr so it goes to stdout (they're not split
up).  Then you pipe the output to the tee program which logs to
GCC.LOG while also printing to the screen (stdout).

> This is the result:
> gcc   -g -O2  -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes
>  -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros
>  -Wold-style-definition   -fomit-frame-pointer -DHAVE_CONFIG_H -I. -I.
>  -I../../gcc-4.0.3/gcc -I../../gcc-4.0.3/gcc/. -I../../gcc-4.0.3/gcc/../include
>  -I../../gcc-4.0.3/gcc/../libcpp/include     \
>   -DGCC_INCLUDE_DIR=\"/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/include\"
> "/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../..`echo /usr | sed -e 's|
> ^/usr||' -e 's|/[^/]*|/..|
> g'`/include/c++/4.0.3\" -DGPLUSPLUS_TOOL_INCLUDE_DIR=
> \"/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../..`echo /usr | sed -e 's|
> ^/usr||' -e 's|/[^/]*|/..|
> g'`/include/c++/4.0.3/i686-pc-linux-gnu\" -DGPLUSPLUS_BACKWARD_INCLUDE_DIR=\
> "/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../..`echo /usr | sed -e 's|
> ^/usr||' -e 's|/[^/]*|/..|
> g'`/include/c++/4.0.3/backward\" -DLOCAL_INCLUDE_DIR=\"/usr/local/include\"
>  -DCROSS_INCLUDE_DIR=\"/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../../i686-pc-linux-gnu/sys-include\"
>  -DTOOL_INCLUDE_DIR=\"/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../../i686-pc-linux-gnu/include\"
> \
>   -c ../../gcc-4.0.3/gcc/cppdefault.c -o cppdefault.o

It looks like what I got.  Unfortunately, that didn't explain
anything.  Just as a last ditch effort, could you run this command:

$ strings /sources/gcc-build/gcc/cppdefault.o

> PS: Might it be an idea to do the build of gcc outside the chroot environment?

No.  You'd end up linking gcc against either your host system or the
temporary system in /tools.  It might build, but it might break later
because it was configured and built for a different system.


More information about the lfs-support mailing list