[1890] in Kerberos_V5_Development
Re: On libdb and shared libraries....
daemon@ATHENA.MIT.EDU (Bill Sommerfeld)
Mon Oct 28 19:58:59 1996
To: "Barry Jaspan" <bjaspan@MIT.EDU>
Cc: tlyu@MIT.EDU, epeisach@MIT.EDU, krbdev@MIT.EDU
In-Reply-To: Your message of "Mon, 28 Oct 1996 14:14:44 -0500 ."
<9610281914.AA18053@DUN-DUN-NOODLES.MIT.EDU>
Date: Mon, 28 Oct 1996 19:48:43 -0500
From: Bill Sommerfeld <sommerfeld@orchard.medford.ma.us>
> This may break Solaris, among other things. If you don't use -l to
> specify shared libraries, the path to the library is *hardcoded* as
> being in the build tree. Setting LD_LIBRARY_PATH won't override it.
> This is not acceptable.
>
> Ummm... gee, that's *wrong*. Shoot whoever implemented it.
I can see the constraints which drove that implementation:
1) need for shared libs in a "wierd" location (not on
LD_LIBRARY_PATH) during development and possibly deployment.
2) need for security in choice of shared libs.
Incidentally, hp-ux has its own strange constraints:
- shared libraries are used straight from location they were in when
the main program was linked, *unless* the +b option is passed to ld
(e.g., -Wl,+b,/lib:/usr/lib:/usr/lib/X11R5) in which case those
directories are searched..
- at link time, you can specifically ask that the binary look for
LPATH (the hpux equiv to LD_LIBRARY_PATH) to be recognized at run
time, but this is *off* by default.
- Bill
