BRIAND, Michel M [EMAIL PROTECTED] writes:
I would like to know why LD_LIBRARY_PATH is evil.
There are many reasons, but one of the biggest ones is that it's a giant
hammer that affects every binary that you run with it set. Even if you
only set it in a wrapper script, it affects every program
Hello Michel,
* BRIAND, Michel M wrote on Tue, Oct 30, 2007 at 05:22:02PM CET:
I would like to know why LD_LIBRARY_PATH is evil.
Because, here, we have several thousand of applications (!) installed on
NFS shares that have each :
- a bin directory
- a lib directory
...
- an environment
Le mercredi 24 octobre 2007 à 18:30 -0500, Bob Friesenhahn a écrit :
On Wed, 24 Oct 2007, Ralf Wildenhues wrote:
I really don't see the need for rpath at all, maybe it makes sense on
other systems, but we are on Linux Solaris.
Well, if I install a shared library in
Hello Wintaki,
* Wintaki Hagabashi wrote on Tue, Oct 23, 2007 at 08:21:57PM CEST:
We are using libtool 1.5.6.
The current release is 1.5.24. Not that it has much to do with your
issue, but otherwise there are many changes since. Please update.
How can we disable libtools use of rpath?
Hi Ralf,
Thanks for the response, much appreciated. Please see my comments below.
* Wintaki Hagabashi wrote on Tue, Oct 23, 2007 at 08:21:57PM CEST:We
are using libtool 1.5.6. The current release is 1.5.24. Not that it has
much to do with your issue, but otherwise there are many
On Wed, 24 Oct 2007, Ralf Wildenhues wrote:
I really don't see the need for rpath at all, maybe it makes sense on
other systems, but we are on Linux Solaris.
Well, if I install a shared library in /opt/foo-package/lib and link a
program against it without an rpath, how will the runtime
