building gcc on i386 for mipsel using uclibc, crtstuff.c can't findlimits.h

[David Wuertele <dave-gnus at bfnet dot com>]

I'm using the uclibc toolchain, building on i386 for a mipsel target.
This works fine for compiling just about everything.  But when I'm
using it to cross compile gcc to make a native gcc for the target, the
crtstuff.c file tries to include limits.h; here's the error I get:

/opt/buildroot/buildroot-3.6.2003/build/staging_dir/bin/mipsel-uclibc-gcc -O2 -DIN_GCC    -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include  -I. -I. -I/opt/buildroot/buildroot-3.6.2003/toolchain_build/gcc-3.2.2/gcc -I/opt/buildroot/buildroot-3.6.2003/toolchain_build/gcc-3.2.2/gcc/. -I/opt/buildroot/buildroot-3.6.2003/toolchain_build/gcc-3.2.2/gcc/config -I/opt/buildroot/buildroot-3.6.2003/toolchain_build/gcc-3.2.2/gcc/../include  -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions  \
   -c /opt/buildroot/buildroot-3.6.2003/toolchain_build/gcc-3.2.2/gcc/crtstuff.c -DCRT_BEGIN \
  -o crtbegin.o
In file included from include/limits.h:11,
                 from /opt/buildroot/buildroot-3.6.2003/toolchain_build/gcc-3.2.2/gcc/tsystem.h:84,
                 from /opt/buildroot/buildroot-3.6.2003/toolchain_build/gcc-3.2.2/gcc/crtstuff.c:62:
/opt/buildroot/buildroot-3.6.2003/build/staging_dir/lib/gcc-lib/mipsel-linux/3.2.2/include/syslimits.h:7:25: no include path in which to find limits.h
/opt/buildroot/buildroot-3.6.2003/toolchain_build/gcc-3.2.2/gcc/crtstuff.c:195: warning: `__EH_FRAME_BEGIN__' defined but not used
make[2]: *** [crtbegin.o] Error 1
make[2]: Leaving directory `/opt/buildroot/buildroot-3.6.2003/build/gcc-target/gcc'
make[1]: *** [all-gcc] Error 2
make[1]: Leaving directory `/opt/buildroot/buildroot-3.6.2003/build/gcc-target'
make: *** [/opt/buildroot/buildroot-3.6.2003/build/gcc-target/.compiled] Error 2

This happens regardless of my host's native gcc version:  I get
identical results on redhat-7.3 and redhat-8.0.

Any suggestions?

Dave


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe at sources dot redhat dot com