From mboxrd@z Thu Jan  1 00:00:00 1970
From: hjl@nynexst.com (H.J. Lu)
To: meissner@cygnus.com (Mike Meissner)
Cc: gas2@cygnus.com, ian@cygnus.com
Subject: Re: Patches to build a shared ELF libbfd.so
Date: Mon, 06 Mar 1995 07:04:00 -0000
Message-id: <9503061456.AA12598@titanic.nynexst.com>
References: <199503061455.JAA01039@tiktok.cygnus.com>
X-SW-Source: 1995/msg00045.html

> 
> | Hi,
> | 
> | I have a patch for gas-950304 to build a shared ELF library,
> | libbfd.so, which contains both libbfd and libopcode. It cuts
> | down the sizes of each ELF binary by several hundred Ks on x86.
> | 
> | But my patch is just a hack since there is no shared library
> | support in binutils. If anyone is interested, I will post
> | my patch. BTW, I think it is a very good test for the ELF
> | support in binutils if you use the binutils to assembler
> | and link itself.
> 
> As I recall, this was discussed last summer.  The problem with making
> bfd a shared library is that the interfaces aren't as cut and dried as

That is one reason why I said "there is no shared library support in
binutils." :-(.

> one would like.  For example, when I was at OSF, we tried to shared
> gdb's bfd with gas/ld in the OSF ODE build evironment.  However,
> because we had not rev'ed GDB for awhile, the calling sequence for the
> disassembling functions had changed, even though the name was the
> same.  In the interest of expediency, I kept gdb's version of bfd in
> the tree along with the assembler and linkers.
> 

Drop me a line if you are interested in fixing it. Hint: proper use of
bfd/VERSION and -soname.


-- 
H.J. Lu
NYNEX Science and Technology, Inc.			hjl@nynexst.com