Re: Cross gcc build problem

[Laine Walker-Avina <lwalkera at ieee dot org>]

On Jul 06, 2007, at 14:31, Brian Dessent wrote:

> Laine Walker-Avina wrote:
>
> > ../build-arm-linux-gnu/libiberty/libiberty.a: could not read symbols:
> > File in wrong format
>
> The build infrastructure is confused about where to use target  
> tools and
> where to use build/host tools.
Yeah, you're right. All of the .o files in libiberty.a are i386-elf  
and not ARM.

> > Here's the configure statement I used:
> > ../src/configure -v --enable-languages=c,c++ --prefix=/usr
> > --enable-shared --with-system-zlib --libexecdir=/usr/lib
> > --without-included-gettext --enable-threads=posix --enable-nls
> > --with-gxx-include-dir=/usr/include/c++/4.1.3 --program-suffix=-4.1
> > --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug
> > --enable-checking=release arm-linux-gnu
>                             ^^^^^^^^^^^^^
>
> This is an ancient and obsolete way of writing --target=arm-linux-gnu.
> I'm not sure if it's the cause of your problem or not, but you should
> definitely spell out --target and not just give a target triplet as a
> naked parameter.
Tried that and it is still building libiberty as i386 and trying to  
link it together with ARM files.
Any clue what would cause this?

> Brian

---
Laine Walker-Avina