
error in loading shared libraries: libXmu.so.6: cannot open shared object
> PATH is not the appropriate variable, LD_LIBRARY_PATH is used to configure
> linked libraries (at least it is on Solaris and I think it works on Linux)
Perhaps is often, but shouldn't be.
LD_LIBRARY_PATH is the most frequently used hack (on many OS)--but a hack.
Most of the time it's easy, works fast and well.
But this variable has highest priority for search order.
(Well, apart from LD_PRELOAD, but that's not usual stuff.)
Thus LD_LIBRARY_PATH is the backdoor for unexpected cases / problems.
In short: one shouldn't need to set LD_LIBRARY_PATH for
the standard applications.
And, if programmers set this variable they won't get used to compile the
search path into the binary (or at least supply a good wrapper).
And, all people using such a badly compiled binary have to adjust
LD_LIBRARY_PATH, too (or write a wrapper). This can lead to conflicts
with binaries, which correctly have compiled in a different path to a
slightly different library, so other wrappers might be needed again
suddenly.
I still have problems from time to time with a site wide LD_LIBRARY_PATH
containing the path to X11 libraries.
ldconfig(8) and the linker option '-rpath'
('-Wl,-rpath' for the gcc frontend) are ones friend.
Binary packages certainly need a wrapper (or ldconfig), as they
and their libraries should be installable at an arbitrary place.
> Newsgroups: comp.os.linux.setup,comp.os.linux
[comp.os.linux is not valid]
Sven