Subject: Re: replacing so libraries - general question
To: None <firstname.lastname@example.org>
From: Frederick Bruckman <email@example.com>
Date: 04/06/2003 15:17:11
On Sun, 6 Apr 2003, Christian Biere wrote:
> Wojciech Puchar <firstname.lastname@example.org> wrote:
> > > Sure, LD_LIBRARY_PATH.
> > >
> > it's completely not what i'm asking.
> As a matter of fact, it is valid solution wrt to your question.
That, by itself, isn't going to let you replace a library with a
library of a *different* *name*. You could use LD_PRELOAD for that.
You could also point the major (libfoo.N) symlink to the new library,
while leaving the actual file (libfoo.N.N) intact, or you could even
do all that in a seperate subdirectory, then point LD_LIBRARY_PATH
into that, leaving your installed system completely intact. Remember,
the ".so" link is used at link-time, the ".so.N" link is used at
run-time (assuming that the SONAME follows convention).
[LD_PRELOAD and LD_LIBRARY_PATH are documented, by the way, in