* [Bug bootstrap/9741] [hppa-linux] ICE (segfault) while building a cross compiler
[not found] <20030218114601.9741.jbglaw@lug-owl.de>
@ 2003-06-15 9:09 ` jbglaw@lug-owl.de
2003-06-15 16:55 ` dhazeghi@yahoo.com
` (2 subsequent siblings)
3 siblings, 0 replies; 4+ messages in thread
From: jbglaw@lug-owl.de @ 2003-06-15 9:09 UTC (permalink / raw)
To: gcc-bugs
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:)
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug bootstrap/9741] [hppa-linux] ICE (segfault) while building a cross compiler
[not found] <20030218114601.9741.jbglaw@lug-owl.de>
2003-06-15 9:09 ` [Bug bootstrap/9741] [hppa-linux] ICE (segfault) while building a cross compiler jbglaw@lug-owl.de
@ 2003-06-15 16:55 ` dhazeghi@yahoo.com
2003-07-18 19:52 ` dhazeghi at yahoo dot com
2003-09-03 5:54 ` pinskia at gcc dot gnu dot org
3 siblings, 0 replies; 4+ messages in thread
From: dhazeghi@yahoo.com @ 2003-06-15 16:55 UTC (permalink / raw)
To: gcc-bugs
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
dhazeghi@yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unknown |3.4
------- Additional Comments From dhazeghi@yahoo.com 2003-06-15 16:55 -------
Hello,
Please in the future include the options you use to configure with when making bootstrap bug
reports.
Building a cross-compiler is unfortunately probably the worst documented part of gcc. The
crossgcc mailing list (http://sources.redhat.com/ml/crossgcc ) probably has the most useful and
current information.
Basically though, you need the headers, and the libraries from the machine you're targetting. Once
you have those installed in a directory (e.g. /usr/local/alpha-linux/build), you'll need to tell gcc
where they are with --with-sysroot=/usr/local/alpha-linux/build for configure. Also take a look at
the cross compiler minihowto (it misses the --with-sysroot but IIRC gets everything else right).
Dara
P.S. If these instructions fix your problem here, I recommend opening a bug essentially stating that
gcc is effectively lacking on-site cross compilation documentation.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug bootstrap/9741] [hppa-linux] ICE (segfault) while building a cross compiler
[not found] <20030218114601.9741.jbglaw@lug-owl.de>
2003-06-15 9:09 ` [Bug bootstrap/9741] [hppa-linux] ICE (segfault) while building a cross compiler jbglaw@lug-owl.de
2003-06-15 16:55 ` dhazeghi@yahoo.com
@ 2003-07-18 19:52 ` dhazeghi at yahoo dot com
2003-09-03 5:54 ` pinskia at gcc dot gnu dot org
3 siblings, 0 replies; 4+ messages in thread
From: dhazeghi at yahoo dot com @ 2003-07-18 19:52 UTC (permalink / raw)
To: gcc-bugs
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
dhazeghi at yahoo dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |build
------- Additional Comments From dhazeghi at yahoo dot com 2003-07-18 19:52 -------
Hello,
this report is currently awaiting feedback. Have you obtained the proper headers to build the cross
compiler? Does it work?
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug bootstrap/9741] [hppa-linux] ICE (segfault) while building a cross compiler
[not found] <20030218114601.9741.jbglaw@lug-owl.de>
` (2 preceding siblings ...)
2003-07-18 19:52 ` dhazeghi at yahoo dot com
@ 2003-09-03 5:54 ` pinskia at gcc dot gnu dot org
3 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2003-09-03 5:54 UTC (permalink / raw)
To: gcc-bugs
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
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |INVALID
------- Additional Comments From pinskia at gcc dot gnu dot org 2003-09-03 05:54 -------
This is invalid as you have to use --with-headers and with the glibc/linux kernel headers
on almost all *-*-linux-gnu.
^ permalink raw reply [flat|nested] 4+ messages in thread