This is the mail archive of the gdb-patches@sourceware.cygnus.com mailing list for the GDB project. See the GDB home page for more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: [gdb 19981224] Enable linking gdb against shared libbfd

To: gdb-patches@cygnus.com
Subject: Re: [gdb 19981224] Enable linking gdb against shared libbfd
From: Jim Blandy <jimb@cygnus.com>
Date: 20 Feb 1999 19:50:31 -0500
Cc: bfd@cygnus.com
References: <199901031957.OAA20819@subrogation.cygnus.com>
Reply-To: gdb-patches@cygnus.com


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?

Follow-Ups:
- Re: [gdb 19981224] Enable linking gdb against shared libbfd
  - From: Ian Lance Taylor <ian@cygnus.com>

References:
- Re: [gdb 19981224] Enable linking gdb against shared libbfd
  - From: Ian Lance Taylor <ian@cygnus.com>

Prev by Date: Re: Native DJGPP (go32) support for gdb 4.17
Next by Date: Re: [gdb 19981224] Enable linking gdb against shared libbfd
Prev by thread: Re: [gdb 19981224] Enable linking gdb against shared libbfd
Next by thread: Re: [gdb 19981224] Enable linking gdb against shared libbfd
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]