[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/14249] Full path to shared object put into binary when it contai
|
From: |
gerhard.pobinger at kapsch dot net |
|
Subject: |
[Bug ld/14249] Full path to shared object put into binary when it contains no SONAME |
|
Date: |
Fri, 15 Jun 2012 13:33:50 +0000 |
http://sourceware.org/bugzilla/show_bug.cgi?id=14249
--- Comment #2 from Gerhard Pobinger <gerhard.pobinger at kapsch dot net>
2012-06-15 13:33:50 UTC ---
I understand that there is a risk of breaking "lots of clients".
I could not find any documentation on this behaviour (=putting the whole path
into DT_NEEDED), so I can imagine others to be as astonished as I was.
The problem I see is that the resulting binary "libmylib.so" will in general
only be runnable on the build machine, since the path cannot be resolved in
another environment. If this is what is intended, it should at least be
documented somewhere as well, shouldn't it?
(ad "add the SONAME"): Changing it's SONAME is difficult, if "libfoo.so" is a
closed-source 3rd-party product.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.