Re: gcc 3.3.4 cross build for mipsel mischooses the `as' to run

[James E Wilson <wilson at specifixinc dot com>]

Samium Gromoff wrote:
> 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
> I.e. instead of running `mipsel-linux-as' it decided to use just plain `as'.

How did you configure binutils?  Your problem indicates that gcc and 
binutils were not configured the same way.  If they were, then gcc would 
have automatically found mipsel-linux-as, even if it wasn't on your 
path.  You need to use the exact same prefix and target configure 
options for binutils and gcc.

Another possible problem here, by specifying the host/build as 
i386-linux, you are actually asking for a canadian cross, assuming that 
you aren't actually using a 20 year old 386 processor to do this build. 
 The rules for canadian crosses are different.  Worst case, you might 
need to build simple crosses native-x-mipsel-linux and 
native-x-i386-linux in order for this to work right.  If you didn't mean 
to do this, then just specify the --target option, and not the 
--host/--build options.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com