gcc cross-compiler for mipsel

[Ralf Corsepius]

On Tue, 2005-07-05 at 01:28 -0400, Ignacio Vazquez-Abrams wrote:
> I'm currently trying to build a cross-compiler toolchain for mipsel
> based on the packages in FC4, and I'm getting the following message when
> running configure for gcc:
> 
> /usr/mipsel-linux/bin/as: symbol lookup error: /usr/mipsel-linux/bin/as:
> undefined symbol: bfd_mips16_num_opcodes
Wild guess (Without having tried to build your packages):

Your binutils seem to be dynamically linked against libbfd.
At runtime you therefore get the libbfd as being shipped by FC, not the
version having been built as part of your toolchain built.

I would assume statically linking your binutils against the libbfd
having been build during building your toolchain (--disable-shared) will
fix this issue.

Another possibility would be to install your toolchain's libbfd outside
of /usr/lib into a target dependent directory and to apply rpath during
linkage.

Finally you could consider to use a different prefix (!= /usr).

> The binutils package I'm using is located here:
> 
> http://fedora.ivazquez.net/files/extras/binutils-mipsel.spec
> http://fedora.ivazquez.net/files/extras/binutils-mipsel-2.15.94.0.2.2-1.src.rpm
> 
> My current gcc-mipsel-minimal specfile, rpmbuild log, and
> obj-mipsel-linux/gcc/config.log are located here:
> 
> http://fedora.ivazquez.net/files/current/
> 
> Does anyone have any idea what is going on, or where I should go for
> further assistance?

The GCC list, the binutils list, the crossgcc list probably are
appropriate.

Also, I'd assume there are enough toolchain developers on this list and
on Extras.

Ralf