On Tue, Mar 14, 2000 at 09:20:26AM -0500, Robert L Krawitz <rlk@xxxxxxxxxxxx> wrote:
> All that ldconfig -n does is create the links. It doesn't update the
> cache. ld.so (at least on Linux) needs the cache:
What you cite is the documentation for ldso-1.9.x, which is not in use on
any current linux system (and has too many bugs to cite here anyway). The
glibc dynamic linker does not suffer from these limitations, and does not
need to have LD_LIBRARY_PATH or an ld.so.cache.
the only problem that can occur is when the soname of a library does not
change, while the library indeed changes. If ldconfig -n is not run, the
link that links the soname -> true file is not up-to-date.
ldconfig -n should therefore (on linux) suffice to make it work, otherwise
there is some bug with libtool, or it's usage.
> My ld.so.conf is correct (if it weren't, running ldconfig wouldn't
> solve the problem)
ld.so.conf is only a hint cache, it is not necessary to find libraries
unless they moved.
I suspect that either ldconfig -n solves the problem, or else the real bug
is still lurking somewhere.
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@xxxxxxxxxxxxx |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
