This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug bootstrap/9741] [hppa-linux] ICE (segfault) while building a cross compiler


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9741



------- Additional Comments From jbglaw@lug-owl.de  2003-06-15 09:09 -------
With gcc-HEAD as of 2003-06-17, 09:10:00 UTC I get that far:

make[2]: Entering directory `/home/jbglaw/build/build-dir/gcc'
for d in libgcc; do \
  if [ -d $d ]; then true; else /bin/sh ../../gcc/gcc/mkinstalldirs $d; fi; \
done
mkdir libgcc
if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi
/home/jbglaw/build/build-dir/gcc/xgcc -B/home/jbglaw/build/build-dir/gcc/
-B/home/jbglaw/bin/alpha-linux/bin/ -B/home/jbglaw/bin/alpha-linux/lib/ -isystem
/home/jbglaw/bin/alpha-linux/include -isystem
/home/jbglaw/bin/alpha-linux/sys-include -O2  -DIN_GCC -DCROSS_COMPILE   -W
-Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem
./include  -fPIC -mieee -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
-D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I../../gcc/gcc
-I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include  -DL_muldi3
-c ../../gcc/gcc/libgcc2.c -o libgcc/./_muldi3.o
In file included from tm.h:5,
                 from ../../gcc/gcc/libgcc2.c:43:
../../gcc/gcc/config/alpha/linux.h:72:20: signal.h: No such file or directory
../../gcc/gcc/config/alpha/linux.h:73:26: sys/ucontext.h: No such file or directory
make[2]: *** [libgcc/./_muldi3.o] Error 1
make[2]: Leaving directory `/home/jbglaw/build/build-dir/gcc'
make[1]: *** [libgcc.a] Error 2
make[1]: Leaving directory `/home/jbglaw/build/build-dir/gcc'
make: *** [all-gcc] Error 2

So it again breaks at a signal include file, but now, it seems to use a correct
one. I've seen this while trying to build other cross compilers (-> for other
architectures), but I never mangaed to really get around that. Googling showed
me that I have to copy target system's header files (libc + (Linux) kernel
./asm-XXX) but I never found a "definitive" guide how to do that and how to tell
this to .../configure ...

Help would be highly appreciated here:)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]