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

> 
> 
>    From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
>    Date: Tue, 29 Dec 1998 20:19:40 +0100 (MET)
> 
>    The following patch is a first shot at linking gdb 19981224 against a
>    shared libbfd (tried on IRIX 6.2).  It has a couple of shortcomings:
> 

I have been using shared libbfd for binutils for a long time
on Linux. I just added "--enable-static=no --enable-shared".
I used it only because libbfd is quite big and there are many
programs in binutils linked against it.

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


H.J.

  parent reply	other threads:[~1999-01-07 17:23 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 [this message]
1999-01-08 15:27     ` Rainer Orth

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=m0zyQe2-00038dC@ocean.lucon.org \
    --to=hjl@lucon.org \
    --cc=bfd@cygnus.com \
    --cc=gdb-patches@cygnus.com \
    --cc=gdb@cygnus.com \
    --cc=ro@TechFak.Uni-Bielefeld.DE \
    --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).