This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
3.2 build failure: i386-pc-linux-gnu cross compiler hosted on i686-pc-cygwin
- From: Aaron Lehmann <aaronl at vitelus dot com>
- To: gcc at gcc dot gnu dot org
- Date: Thu, 15 Aug 2002 19:55:07 -0700
- Subject: 3.2 build failure: i386-pc-linux-gnu cross compiler hosted on i686-pc-cygwin
/home/unknown/gcc-3.2/gcc/xgcc -B/home/unknown/gcc-3.2/gcc/
-B/usr/local/i386-pc-linux-gnu/i386-pc-linux-gnu/bin/
-B/usr/local/i386-pc-linux-gnu/i386-pc-linux-gnu/lib/ -isystem
/usr/local/i386-pc-linux-gnu/i386-pc-linux-gnu/include -O2 -DIN_GCC
-DCROSS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT
-DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I. -I./.
-I./config -I./../include -DL_muldi3 -c ./libgcc2.c -o
libgcc/./_muldi3.o
In file included from tconfig.h:22,
from libgcc2.c:36:
config/i386/linux.h:224:20: signal.h: No such file or directory
config/i386/linux.h:225:26: sys/ucontext.h: No such file or directory
make[2]: *** [libgcc/./_muldi3.o] Error 1
make[2]: Leaving directory `/home/unknown/gcc-3.2/gcc'
make[1]: *** [libgcc.a] Error 2
make[1]: Leaving directory `/home/unknown/gcc-3.2/gcc'
make: *** [all-gcc] Error 2
gcc seems to want linux-specific headers to build a cross compiler
targeted at linux. Is this correct behavior?