Error while building cross-compiler...
Edward L. Hepler
elh@ece.vill.edu
Fri Nov 5 06:14:00 GMT 1999
I am attempting to build a cross compiler using gcc-2.95.2
Here is the sequence that I performed:
mkdir arm_obj
cd arm_obj
../configure --prefix=/export/home/asic8_disk1/cwhome/heplerel/env --target=arm-arm-coff --with-gnu-as --with-gnu-ld --enable-haifa
make all
Everything seems OK until the make gets to the section where header files
are "fixed"... Then the following log is produced:
touch s-mlib
gcc -DCROSS_COMPILE -DIN_GCC -DHAIFA -DSVR4 -g -O2 -DHAVE_CONFIG_H -I. -I../../gcc -I../../gcc/config -I../../gcc/../include \
-DSTANDARD_STARTFILE_PREFIX=\"/export/home/asic8_disk1/cwhome/heplerel/env/lib/\" -DSTANDARD_EXEC_PREFIX=\"/export/home/asic8_disk1/cwhome/heplerel/env/lib/gcc-lib/\" -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"arm-arm-coff\" -DTOOLDIR_BASE_PREFIX=\"/export/home/asic8_disk1/cwhome/heplerel/env/\" \
-c `echo ../../gcc/gcc.c | sed 's,^\./,,'`
gcc -DCROSS_COMPILE -DIN_GCC -DHAIFA -DSVR4 -g -O2 -DHAVE_CONFIG_H -o xgcc gcc.o gccspec.o intl.o \
prefix.o version.o obstack.o alloca.o ../libiberty/libiberty.a
rm -rf include; mkdir include
TARGET_MACHINE=arm-arm-coff; srcdir=`cd ../../gcc; pwd`; \
INSTALL_ASSERT_H=install-assert-h; SHELL=/bin/sh ;\
export TARGET_MACHINE srcdir INSTALL_ASSERT_H SHELL ; \
/bin/sh ./fixinc.sh `pwd`/include /export/home/asic8_disk1/cwhome/heplerel/env/arm-arm-coff/sys-include
Fixing headers into /export/home/asic8_disk1/cwhome/heplerel/env/src/GNU/gcc-2.95.2/arm_obj/gcc/include for arm-arm-coff target
./fixinc.sh: /export/home/asic8_disk1/cwhome/heplerel/env/arm-arm-coff/sys-include: does not exist
make[1]: *** [stmp-fixinc] Error 1
make[1]: Leaving directory `/export/home/asic8_disk1/cwhome/heplerel/env/src/GNU/gcc-2.95.2/arm_obj/gcc'
make: *** [all-gcc] Error 2
I suspect that I have not done something that I should have... although I
don't remember having a problem like this when creating a cross compiler
for the mc68000 using a slightly earlier version of gcc...
It appears that the make is attempting to find some files "to fix" that
do not exist... Should I have moved some files prior to doing the make?
Thanks,
Ed Hepler
More information about the Gcc-bugs
mailing list