This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Problems building a cross compiler (toolchain)
- To: rutt at tensilica dot com
- Subject: Re: Problems building a cross compiler (toolchain)
- From: hjl at lucon dot org (H.J. Lu)
- Date: Sat, 28 Mar 1998 09:32:11 -0800 (PST)
- Cc: egcs at cygnus dot com
>
> I'm trying to build a cross compiler i686-linux -> mips-elf. I tried to
> follow the instructions in
> ftp://ftp.cygnus.com/pub/embedded/crossgcc/FAQ-0.8.1, but perhaps I haven't
> done as well as I could. I'll give the exact steps I followed at the end of
> the message.
>
I will look into this if it is still not solved next week.
> The problem is that the make of egcs errors out with:
>
> GNU assembler version 2.8.1 (mips-elf), using BFD version 2.8.1
> mips-tfile -v -o _muldi3.o /tmp/cca01170.s
> xgcc: installation problem, cannot exec `mips-tfile': No such file or directory
>
> This happens when it is trying to compile _muldi3.o with the following
> command:
>
> /home/rutt/src/egcs-1.0.2/mips/gcc/xgcc \
> -B/home/rutt/src/egcs-1.0.2/mips/gcc/ -O2 -DCROSS_COMPILE -DIN_GCC \
> -g -O2 -I./include -G 0 -g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED \
> -fexceptions -I. -I../../gcc -I../../gcc/config -c -DL_muldi3 \
> ../../gcc/libgcc2.c -o _muldi3.o -v
>
> I found the source to mips-tfile in the egcs tree, but I can't build it:
>
> [rutt@gertie gcc]$ make mips-tfile
> gcc -c -DCROSS_COMPILE -DIN_GCC -g -DHAVE_CONFIG_H -I. -I../../gcc -I../../gcc/config ../../gcc/mips-tfile.c
> ../../gcc/mips-tfile.c:719: mips/a.out.h: No such file or directory
>
> >From glancing at it, I don't understand why I should need it. It seems to be
> a COFF thing.
>
> Here are the steps I followed:
>
> 1. cd binutils-2.8.1
> 2. configure --target=mips-elf --host=i686-linux -prefix=/home/rutt/cross/mips
> 3. make all install
> 4. cd ../egcs-1.0.2
> 5. mkdir mips
> 6. ../configure --target=mips-elf --host=i686-linux -prefix=/home/rutt/cross/mips
> 7. make cross
>
Are you using glibc 2? If you are not sure, I would recommend to leave
out the --host part and let configure figure out what your host is.
--
H.J.