tech-toolchain archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: "Fixing" new ld(1) DT_NEEDED handling
On Mon, Oct 14, 2013 at 05:29:59PM +0400, Valery Ushakov wrote:
>
> And then I wrote:
>
> | Hmm, using http://fedoraproject.org/wiki/UnderstandingDSOLinkChange
> | example on Solaris 11:
> |
> | $ gcc --verbose -o foo1 foo1.o -L. foo2.so
> | [...]
> | ld: Software Generation Utilities - Solaris Link Editors: 5.11-1.2324
> | Undefined first referenced
> | symbol in file
> | foo foo1.o (symbol belongs to implicit dependency ./foo3.so)
> | ld: fatal: symbol referencing errors. No output written to foo1
>
> So the symbol is NOT resolved.
Hmmm... I'm fairle sure it hadn't used to behave that way.
The SYSV linker definetely didn't.
I've written 'dummy' .so that only have an SO_NAME and a DT_NEEDED
entry in order to link programs with a specific DT_NEEDED entry
(typically with an absolute path).
This now seems to be impossible.
David
--
David Laight: david%l8s.co.uk@localhost
Home |
Main Index |
Thread Index |
Old Index