This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Cross-compile error
- From: Brandon Falk <bfalk at gamozolabs dot com>
- To: gcc-help at gcc dot gnu dot org
- Date: Sat, 5 Jan 2013 18:39:17 -0500
- Subject: Cross-compile error
I'm currently working on a buildsystem
(http://gamozolabs.com/gamozoland) for creating build environments
that can be chroot into and everything in that chroot is targeted to a
specific target.
I'm able to build with:
GL_BUILD = x86_64-linux-gnu
GL_HOST = x86_64-linux-gnu
GL_TARGET = x86_64-linux-gnu
With no problems. (These parameters are directly passed to configure
as --build, --host, --target)
However, with:
GL_BUILD = x86_64-linux-gnu
GL_HOST = x86_64-linux-gnu
GL_TARGET = arm-linux-androideabi
Configure:
PROJ_CFG = --build=$(GL_BUILD) --host=$(GL_HOST) --target=$(GL_TARGET) \
--enable-languages=c,c++ --prefix=/usr
I'm getting the error:
make[6]: Entering directory
`/home/buildy/gamozoland/build/x86_64-linux-gnu/arm-linux-androideabi/gcc-4.7.2/arm-linux-androideabi/armv7-a/libgcc'
# If this is the top-level multilib, build all the other
# multilibs.
/home/buildy/gamozoland/build/x86_64-linux-gnu/arm-linux-androideabi/gcc-4.7.2/./gcc/xgcc
-B/home/buildy/gamozoland/build/x86_64-linux-gnu/arm-linux-androideabi/gcc-4.7.2/./gcc/
-B/usr/arm-linux-androideabi/bin/ -B/usr/arm-linux-androideabi/lib/
-isystem /usr/arm-linux-androideabi/include -isystem
/usr/arm-linux-androideabi/sys-include -g -O2 -march=armv7-a -O2
-g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing
-Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition -isystem ./include -fPIC -fno-inline -g
-DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -Dinhibit_libc
-fPIC -fno-inline -I. -I. -I../../.././gcc
-I../../../../../../../srcs/gcc/gcc-4.7.2/libgcc
-I../../../../../../../srcs/gcc/gcc-4.7.2/libgcc/.
-I../../../../../../../srcs/gcc/gcc-4.7.2/libgcc/../gcc
-I../../../../../../../srcs/gcc/gcc-4.7.2/libgcc/../include
-DHAVE_CC_TLS -o emutls.o -MT emutls.o -MD -MP -MF emutls.dep
-fexceptions -c
../../../../../../../srcs/gcc/gcc-4.7.2/libgcc/emutls.c
-fvisibility=hidden -DHIDE_EXPORTS
In file included from
../../../../../../../srcs/gcc/gcc-4.7.2/libgcc/gthr.h:150:0,
from
../../../../../../../srcs/gcc/gcc-4.7.2/libgcc/emutls.c:31:
./gthr-default.h:41:21: fatal error: pthread.h: No such file or directory
compilation terminated.
make[6]: *** [emutls.o] Error 1
make[6]: Leaving directory
`/home/buildy/gamozoland/build/x86_64-linux-gnu/arm-linux-androideabi/gcc-4.7.2/arm-linux-androideabi/armv7-a/libgcc'
make[5]: *** [multi-do] Error 1
make[5]: Leaving directory
`/home/buildy/gamozoland/build/x86_64-linux-gnu/arm-linux-androideabi/gcc-4.7.2/arm-linux-androideabi/libgcc'
make[4]: *** [all-multi] Error 2
make[4]: Leaving directory
`/home/buildy/gamozoland/build/x86_64-linux-gnu/arm-linux-androideabi/gcc-4.7.2/arm-linux-androideabi/libgcc'
make[3]: *** [all-target-libgcc] Error 2
make[3]: Leaving directory
`/home/buildy/gamozoland/build/x86_64-linux-gnu/arm-linux-androideabi/gcc-4.7.2'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/buildy/gamozoland/build/x86_64-linux-gnu/arm-linux-androideabi/gcc-4.7.2'
If it can't find pthread.h, then I'm assuming there is some issue with
glibc... but how could I possibly build glibc without gcc in the first
place?
-Brandon