This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: LD_LIBRARY_PATH

From: Geoff Keating <geoffk at geoffk dot org>
To: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
Cc: Anders Lennartsson <anders dot lennartsson at foi dot se>, gcc at gcc dot gnu dot org
Date: 23 Nov 2002 11:43:34 -0800
Subject: Re: LD_LIBRARY_PATH
References: <Pine.BSF.4.44.0210232333250.69575-100000@pulcherrima.dbai.tuwien.ac.at>

Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:

> This is an issue coming up again and again, and it really seems to
> burn users, especially since we switched to libgcc_s.so.
> 
> http://gcc.gnu.org/java/build-snapshot.html already has a bit on
> LD_LIBRARY_PATH, though I believe we also need something in our main
> installation documentation.
> 
> The questions is: What exactly do we want to document, and how?  Do
> we just want to state
> 
>   After the installation, you will probably need to add $prefix/lib
>   to LD_LIBRARY_PATH, so that dynamic executable can locate their
>   libraries
> 
> or something more elaborate?

If we do want something more descriptive, the rule is that libraries
from newer versions of GCC should be preferred over libraries from
earlier versions, but when the libraries don't conflict, both should
be installed.  This can be done by using LD_LIBRARY_PATH, or by
copying the files into appropriate locations, or a bunch of other
ways depending on the user's system configuration.

-- 
- Geoffrey Keating <geoffk@geoffk.org>

References:
- LD_LIBRARY_PATH
  - From: Gerald Pfeifer

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]