[1895] in Kerberos_V5_Development
Re: On libdb and shared libraries....
daemon@ATHENA.MIT.EDU (Tom Yu)
Mon Oct 28 23:33:49 1996
Date: Mon, 28 Oct 1996 23:33:40 -0500
To: Kev <klmitch@MIT.EDU>
Cc: Ezra Peisach <epeisach@MIT.EDU>, "Theodore Y. Ts'o" <tytso@MIT.EDU>,
Tom Yu <tlyu@MIT.EDU>, "Barry Jaspan" <bjaspan@MIT.EDU>,
krbdev@MIT.EDU
From: Tom Yu <tlyu@MIT.EDU>
In-Reply-To: <199610290425.XAA32253@integrity.mit.edu>
>>>>> "Kev" == Kev <klmitch@MIT.EDU> writes:
Kev> if I may ask, what precisely is this problem?
The problem doesn't exist under our current build system. If we were
to specify explicit paths to the shared libraries that we were
linking, then it could potentially be a problem.
Basically, if you specify an explicit path to a shared library when
you're linking a program, and there is no SONAME record in the shared
library, the linker records the *absolute* path and filename of the
shared library, and you can't override this with LD_RUN_PATH or -R. I
was seeing this failure when I experimented with absolute paths to
shared libraries because I was using gcc, which we currently do not
allow to stuff the SONAME record of the shared library file.
---Tom
