This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: gcc 3.3.4 cross build for mipsel mischooses the `as' to run
- From: "Dave Korn" <dk at artimi dot com>
- To: <gcc at gcc dot gnu dot org>
- Date: Wed, 4 Aug 2004 17:44:46 +0100
- Subject: RE: gcc 3.3.4 cross build for mipsel mischooses the `as' to run
> -----Original Message-----
> From: gcc-owner On Behalf Of Samium Gromoff
> Sent: 04 August 2004 16:39
> I`ve got a trouble while crossbuilding gcc-3.3.4 for mipsel.
>
> I configured gcc like that:
>
> canopus:/src/gcc-obj$ ../gcc-3.3.4/configure
> --prefix=/opt/elcore --host=i386-linux --build=i386-linux
> --target=mipsel-linux
>
> That`s what happened:
> as: unrecognized option `-EL'
> make[1]: *** [crtbegin.o] Error 1
> make[1]: Leaving directory `/src/gcc-obj/gcc'
> make: *** [all-gcc] Error 2
You forgot to do
export PATH=${prefix}/bin:$PATH
after installing the cross binutils and before configuring/building gcc.
> I.e. instead of running `mipsel-linux-as' it decided to use
> just plain `as'.
I'm not sure the exact algorithm used by the configure/build process, but
yes, if it can't find ${target}-as in the $PATH, it falls back to just
searching for as (without any prefix), and hopes that the first one it finds
is the one it needs.
I don't know why the configure/build process doesn't think to look in
${prefix}/bin, since it's a documented requirement that ${prefix} is
specified the same for gcc as for the requisite binutils.
cheers,
DaveK
--
Can't think of a witty .sigline today....