From: Ian Lance Taylor <ian@cygnus.com>
To: jimb@cygnus.com
Cc: gdb-patches@cygnus.com, bfd@cygnus.com
Subject: Re: [gdb 19981224] Enable linking gdb against shared libbfd
Date: Sun, 21 Feb 1999 17:10:00 -0000 [thread overview]
Message-ID: <199902220110.UAA03133@subrogation.cygnus.com> (raw)
In-Reply-To: <npr9rk1sx4.fsf@zwingli.cygnus.com>
From: Jim Blandy <jimb@cygnus.com>
Date: 20 Feb 1999 19:50:31 -0500
In a long-ago discussion on whether GDB should use a shared BFD, Ian
Taylor said:
> Correct: there are no current plans to use -release when building a
> BFD shared library.
>
> I believe the correct solution for BFD is to rename the shared library
> based on the BFD version number. However, this is not currently
> implemented.
Why is including the BFD version in the shared library name preferable
to using -release?
I'm not sure just what I was thinking, as the current BFD sources
actually do use -release. See libbfd_la_LDFLAGS in bfd/Makefile.am.
I was probably confused. Perhaps I was confusing -release and
-version-info.
I do believe that there is a current problem with BFD shared
libraries, which is that the name of the shared library does not
reflect the configured target. The effect is that you can not
configure BFD more than once with different targets but with the same
prefix.
Ian
next prev parent reply other threads:[~1999-02-21 17:10 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 [this message]
1999-01-07 17:23 ` H.J. Lu
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=199902220110.UAA03133@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=bfd@cygnus.com \
--cc=gdb-patches@cygnus.com \
--cc=jimb@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).