This is the mail archive of the
binutils@sourceware.cygnus.com
mailing list for the binutils project.
Re: Building cross development tools...
- To: scottb at netwinder dot org
- Subject: Re: Building cross development tools...
- From: Ian Lance Taylor <ian at zembu dot com>
- Date: 19 Nov 1999 14:40:34 -0500
- CC: binutils at sourceware dot cygnus dot com
- References: <3835A4EB.CF06B33@netwinder.org>
Date: Fri, 19 Nov 1999 14:28:43 -0500
From: Scott Bambrough <scottb@netwinder.org>
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.
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.
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.
Ian