This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Cross compiler (alpha-linux on cygwin host) build problems
- From: Roman Belenov <rbelenov at yandex dot ru>
- To: gcc at gcc dot gnu dot org
- Date: Thu, 15 May 2003 11:54:00 +0400
- Subject: Cross compiler (alpha-linux on cygwin host) build problems
I'm trying to setup compiler for alpha-dec-linux target on Cygwin
host. The problem is that during compilation of libgcc I get
------------------------------------------------------------------------
/build/gcc/gcc/xgcc -B/build/gcc/gcc/
-B/usr/local/cross/alpha/alpha-dec-linux/bin/
-B/usr/local/cross/alpha/alpha-dec-linux/lib/ -isystem
/usr/local/cross/alpha/alpha-dec-linux/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/cygdrive/e/tmp/2/gcc-3.3/gcc
-I/cygdrive/e/tmp/2/gcc-3.3/gcc/. -I/cygdrive/e/tmp/2/gcc-3.3/gcc/config
-I/cygdrive/e/tmp/2/gcc-3.3/gcc/../include -DL_muldi3 -c
/cygdrive/e/tmp/2/gcc-3.3/gcc/libgcc2.c -o libgcc/./_muldi3.o
In file included from tconfig.h:19,
from /cygdrive/e/tmp/2/gcc-3.3/gcc/libgcc2.c:36:
/cygdrive/e/tmp/2/gcc-3.3/gcc/config/alpha/linux.h:68:20: signal.h: No
such file or directory
/cygdrive/e/tmp/2/gcc-3.3/gcc/config/alpha/linux.h:69:26:
sys/ucontext.h: No such file or directory
make[2]: *** [libgcc/./_muldi3.o] Error 1
make[2]: Leaving directory `/build/gcc/gcc'
make[1]: *** [libgcc.a] Error 2
make[1]: Leaving directory `/build/gcc/gcc'
make: *** [all-gcc] Error 2
------------------------------------------------------------------------
so that it seems that glibc is required to compile libgcc. Since I
don't have target glibc yet I tried to extract required headers from
glibc source manually, but found this task nontrivial (I stopped when
according to my assumptions one file had to #include_next another one
located at exactly the same place - probably I just don't correctly
grok directory structure of glibc headers). Is there some
(semi)automatic way to overcome this problem ? Any pointers are
appreciated (I looked through several cross-compilation pages, but it
seems that libgcc was self-sufficient for targets described).
--
With regards, Roman.