Problems compiling gcc

Chris Staub chris at beaker67.com
Fri Jun 29 10:10:53 PDT 2007


Robert Jakob wrote:
> Hello,
> 
> I am using LFS Version 6.2 and I have problems compiling gcc for the 
> third time, after chrooting.
> Problems occur suddenly in the middle of compiling process. It seems 
> that the compiler does not find the
> system include files anymore. Here is the compiler output (when starting 
> make again):
> 
>  >> cut here <<
> 
> make[1]: Entering directory `/sources/gcc-build-3/libiberty'
> make[2]: Entering directory `/sources/gcc-build-3/libiberty/testsuite'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory `/sources/gcc-build-3/libiberty/testsuite'
> make[1]: Leaving directory `/sources/gcc-build-3/libiberty'
> make[1]: Entering directory `/sources/gcc-build-3/fixincludes'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/sources/gcc-build-3/fixincludes'
> make[1]: Entering directory `/sources/gcc-build-3/intl'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/sources/gcc-build-3/intl'
> make[1]: Entering directory `/sources/gcc-build-3/build-i686-pc-linux-gnu/libiberty'
> make[2]: Entering directory `/sources/gcc-build-3/build-i686-pc-linux-gnu/libiberty/testsuite'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory `/sources/gcc-build-3/build-i686-pc-linux-gnu/libiberty/testsuite'
> make[1]: Leaving directory `/sources/gcc-build-3/build-i686-pc-linux-gnu/libiberty'
> make[1]: Entering directory `/sources/gcc-build-3/build-i686-pc-linux-gnu/fixincludes'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/sources/gcc-build-3/build-i686-pc-linux-gnu/fixincludes'
> make[1]: Entering directory `/sources/gcc-build-3/libcpp'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/sources/gcc-build-3/libcpp'
> make[1]: Entering directory `/sources/gcc-build-3/gcc'
> /sources/gcc-build-3/gcc/xgcc -B/sources/gcc-build-3/gcc/ -B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include -isystem /usr/i686-pc-linux-gnu/sys-include -O2 -DIN_GCC    -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem ./include  -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   -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-unit-at-a-time -fno-omit-frame-pointer \
>    -c ../../gcc-4.0.3/gcc/crtstuff.c -DCRT_BEGIN \
>   -o crtbegin.o
> In file included from ../../gcc-4.0.3/gcc/crtstuff.c:64:
> ../../gcc-4.0.3/gcc/tsystem.h:90:19: error: stdio.h: No such file or directory
> ../../gcc-4.0.3/gcc/tsystem.h:93:23: error: sys/types.h: No such file or directory
> ../../gcc-4.0.3/gcc/tsystem.h:96:19: error: errno.h: No such file or directory
> ../../gcc-4.0.3/gcc/tsystem.h:103:20: error: string.h: No such file or directory
> ../../gcc-4.0.3/gcc/tsystem.h:104:20: error: stdlib.h: No such file or directory
> ../../gcc-4.0.3/gcc/tsystem.h:105:20: error: unistd.h: No such file or directory
> In file included from /sources/gcc-build-3/gcc/include/syslimits.h:7,
>                  from /sources/gcc-build-3/gcc/include/limits.h:11,
>                  from ../../gcc-4.0.3/gcc/tsystem.h:108,
>                  from ../../gcc-4.0.3/gcc/crtstuff.c:64:
> /sources/gcc-build-3/gcc/include/limits.h:122:61: error: limits.h: No such file or directory
> In file included from ../../gcc-4.0.3/gcc/crtstuff.c:64:
> ../../gcc-4.0.3/gcc/tsystem.h:111:18: error: time.h: No such file or directory
> make[1]: *** [crtbegin.o] Error 1
> make[1]: Leaving directory `/sources/gcc-build-3/gcc'
> make: *** [all-gcc] Error 2
> 
>  >> cut here <<
> 
> As far as I looked for it, the include directorys for the system 
> variables point to /usr/i686-pc-linux-gnu, but this directory
> does not exit on my filesystem. The quere thing is, that it compiles 
> succesfully for 45 minutes before, finding all the necessary
> include files.
> 
> I tried make clean twice, but it stops always on the same error.
> The installation of the things before went well. The checks had no quere 
> errors or s.th.
> 
> Has anyone any idea what I could/should do?
> Perhaps creating a symlink /usr/i686-pc-linux-gnu to something?
> 
> //Thanks for all answers
> 
> Greetz
>     Robert
> 
> //

No, do not create any symlinks. The most likely cause of this problem is 
that you either forgot to remove the gcc source and build dirs after 
compiling pass 2, or you applied the specs patch.



More information about the lfs-support mailing list