public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Mike Meissner <meissner@cygnus.com>
To: hjl@nynexst.com
Cc: gas2@cygnus.com, ian@cygnus.com
Subject: Patches to build a shared ELF libbfd.so
Date: Mon, 06 Mar 1995 06:55:00 -0000	[thread overview]
Message-ID: <199503061455.JAA01039@tiktok.cygnus.com> (raw)
In-Reply-To: <9503051555.AA10263@titanic.nynexst.com>

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

-- 
Michael Meissner, Cygnus Support (East Coast)
Suite 105, 48 Grove Street, Somerville, MA 02144, USA
meissner@cygnus.com,	617-629-3016 (office),	617-629-3010 (fax)


  reply	other threads:[~1995-03-06  6:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-03-06  6:15 H.J. Lu
1995-03-06  6:55 ` Mike Meissner [this message]
1995-03-06  7:04   ` H.J. Lu
1995-03-06  7:42 ` Ian Lance Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199503061455.JAA01039@tiktok.cygnus.com \
    --to=meissner@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=hjl@nynexst.com \
    --cc=ian@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).