Alan Modra amodra@bigpond.net.au
Sun Mar 2 23:00:00 GMT 2003

• Previous message (by thread): [RFC] BFD library installation
• Next message (by thread): [PATCH] MIPS gas: Remove non-BFD_ASSEMBLER cases
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Sun, Mar 02, 2003 at 04:45:41PM +0100, Svein E. Seldal wrote:
> What is the exact motivation behind...
> 1) ... not installing libbfd.a per default when compiling cross targets.
> 2) ... installing the bfd library under a machine-specific directory.

The reason is that libbfd.a is both host and target specific, being
code compiled for the host to support the target.  Thus the motivation
for 1) is that we didn't want to overwrite the native libbfd.a (at one
stage libbfd.a installed to $prefix/lib regardless of target), and the
answer to 2) is to allow different host/target dependent libs to
coexist on a system.  I'll admit the scheme could well be improved,
eg. --enable-targets=all --enable-64-bit-bfd is hardly target
dependent.

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

---

• Previous message (by thread): [RFC] BFD library installation
• Next message (by thread): [PATCH] MIPS gas: Remove non-BFD_ASSEMBLER cases
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Binutils mailing list