[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: small problem building 2.2.17 with BerkeleyDB.4.2

Quoting Tony Earnshaw <tonye@billy.demon.nl>:

> > I understand AIX and HP-UX call the "linkage loader library path"
> > differently, but was not aware that Linux and FreeBSD use the same
> > "LD_LIBRARY_PATH" name as Solaris, and incorrectly thought that this
> > environment variable is only "specific" to Solaris.
> To keep on topic, my experience after having compiled on RH Linux for
> several years, is that as far as Openldap is concerned, LD_LIBRARY_PATH,
> although the variable exists, often doesn't work in practice and the
> directory path has to be entered into ld.so.conf and ldconfig run.
> Having to use LD_LIBRARY_PATH at all is, for me, an admission that I'm
> doing something wrong :)

There are many ways of linking and every system uses a different method.  From
my (limited) experience, i have noted solaris sysadmins have historically tended
to use LD_LIBRARY_PATH as a primary method for pointing to libs, although
'recently' use of the crle command has become more widespread, which works much
like ldconfig in linux, and LD_LIBRARY_PATH has never seemed to do anything for
me in Linux.  Usage of LD_LIBRARY_PATH can cause subtle problems, particularly
if you have multiple library versions, whereas crle/ldconfig way of doing things
is fairly dynamic and you don't have to specify things at compile time. 
Personally, on Solaris I always link with -R which hints the resulting binary
towards the runtime lib path - i find this is the only reliable method of
avoiding library clashes.

This message was penned by the hand of Dom