Re: Building cross development tools...

["Maciej W. Rozycki" <macro at ds2 dot pg dot gda dot pl>]

On 19 Nov 1999, Ian Lance Taylor wrote:

> 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 am using the following options to ./configure: "--enable-shared
--disable-static
--libdir='${exec_prefix}'/<target_alias>/<host_alias>/lib", which produces
shared libraries only.  This approach actually works because libtool
hardcodes library paths into binaries (using RPATH tag), if linked against
libraries located in a non-standard place.  This probably does not work
for non-ELF hosts, but I do not care for now.

> 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.

 Not a bad idea, in fact.  Now that binutils use libtool it should be
quite easy to implement.  I'll look into the problem when time permits.

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +