public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
* Overriding a DT_SONAME
@ 2005-04-13 23:35 Mike Hearn
  2005-04-15  6:24 ` Alan Modra
  0 siblings, 1 reply; 2+ messages in thread
From: Mike Hearn @ 2005-04-13 23:35 UTC (permalink / raw)
  To: binutils

Hi,

I would like to link against a library, say libfoo with soname
libfoo.so.0, but in my executable I'd like the DT_NEEDED entry to be
recorded as some other name, eg libfoo.myapp.so.0 so at install time I can
use a symlink to point the executable somewhere else.

Is there a way to make ld link against a given library, but break the
DT_NEEDED == DT_SONAME relationship without actually recompiling the
target library with a custom soname? Or does it involve binary edits?

thanks -mike

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Overriding a DT_SONAME
  2005-04-13 23:35 Overriding a DT_SONAME Mike Hearn
@ 2005-04-15  6:24 ` Alan Modra
  0 siblings, 0 replies; 2+ messages in thread
From: Alan Modra @ 2005-04-15  6:24 UTC (permalink / raw)
  To: Mike Hearn; +Cc: binutils

On Thu, Apr 14, 2005 at 12:44:24AM +0100, Mike Hearn wrote:
> I would like to link against a library, say libfoo with soname
> libfoo.so.0, but in my executable I'd like the DT_NEEDED entry to be
> recorded as some other name, eg libfoo.myapp.so.0 so at install time I can
> use a symlink to point the executable somewhere else.
> 
> Is there a way to make ld link against a given library, but break the
> DT_NEEDED == DT_SONAME relationship without actually recompiling the
> target library with a custom soname?

No.

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-04-15  6:24 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-04-13 23:35 Overriding a DT_SONAME Mike Hearn
2005-04-15  6:24 ` Alan Modra

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