Re: Building cross development tools...

[Scott Bambrough <scottb at netwinder dot org>]

Ian Lance Taylor wrote:
> 
>    When I build binutils with --prefix=/usr --host=i586-unknown-linux-gnu
>    --target=arm-linux on x86 and install I  get the following files
>    installed:
> 
>    in /usr/include:
>    ansidecl.h, bfd.h, bfdlink.h
> 
>    in /usr/lib:
>    libiberty.a
>    libbfd.a, libbfd.la
>    libopcodes.a, libopcodes.la
> 
>    Is this correct?  Won't these screw up the native build and run
>    environment?  I'm assuming I'm missing something, and I'd appreciate
>    knowing what.
> 
> The files in /usr/include don't matter, because they are the same on
> all systems.  Same with /usr/lib/libiberty.a.

Yeah, I figured that about the headers, but wouldn't libiberty.a contain
ARM code in this case?  That would screw up the native build environment
too I would think.  The static lib with x86 code would be overwritten.

> The libbfd and libopcodes files are theoretically a problem.  For a
> while I think we were installing those using a target name, but I
> guess we stopped.  Very few programs expect to use the installed
> libraries, so most people don't worry about this.  It would be worse
> if you installed a shared library.

True.

> I would accept patches to install the libraries under a name which
> included the target, provided they were well tested, particularly when
> configuring with --enable-shared.

Ok.  Thanks for the help.  I appreciate it.

Scott

-- 
Scott Bambrough - Software Engineer
REBEL.COM    http://www.rebel.com
NetWinder    http://www.netwinder.org