public inbox for bfd@sourceware.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: hjl@lucon.org (H.J. Lu)
Cc: shebs@cygnus.com (Stan Shebs),
	gdb-patches@cygnus.com, gdb@cygnus.com, bfd@cygnus.com
Subject: Re: [gdb 19981224] Enable linking gdb against shared libbfd
Date: Fri, 08 Jan 1999 15:27:00 -0000	[thread overview]
Message-ID: <13974.37950.226281.104005@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: <m0zyQe2-00038dC@ocean.lucon.org>

H.J. Lu writes:

> However, the ABI of libbfd changes quite often. A system
> wide libfd may not work very well. You may not use libbfd from
> binutils 2.9.1 with gdb 19981224. If you are suggesting make

that's why I asked about proper library versioning and interface stability
in libbfd.  But the responses indicate that this won't happen for quite
some time, if at all.

> libbfd in gdb shared, I don't see any benefit to do so since
> the shared libbfd may only be safely used with the gdb where
> the libbfd comes from. Also on Linux, I make the whole gdb binary
> static. It is very useful when you work on C libraries.

:-)  But generally unnecessary on commercial Unixes.  As I said, if you
could share one libbfd between binutils and gdb, that would save some
space.

	Rainer

      reply	other threads:[~1999-01-08 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <13961.11084.647489.224494@xayide.TechFak.Uni-Bielefeld.DE>
1998-12-30 13:55 ` Stan Shebs
1999-01-03 11:58   ` Ian Lance Taylor
1999-02-20 16:50     ` Jim Blandy
1999-02-21 17:10       ` Ian Lance Taylor
1999-01-07 17:23   ` H.J. Lu
1999-01-08 15:27     ` Rainer Orth [this message]

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=13974.37950.226281.104005@xayide.TechFak.Uni-Bielefeld.DE \
    --to=ro@techfak.uni-bielefeld.de \
    --cc=bfd@cygnus.com \
    --cc=gdb-patches@cygnus.com \
    --cc=gdb@cygnus.com \
    --cc=hjl@lucon.org \
    --cc=shebs@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).