On Wed, Jul 05, 2006 at 01:04:55PM EDT, Thomas Adam wrote:
> On Wed, Jul 05, 2006 at 06:46:49PM +0200, Laurent MONIN wrote:
> > This is done in current git tree
> > (7e6c98dadfe58a407382737b47e31fa7485a4c06). I think you mean
> > /etc/ld.so.conf instead of /etc/ldconfig.so.conf, am i wrong ?
> 
> /etc/ld.so.conf, and note that adding "/usr/local/lib" should go at the
> end of the file, if *at all*.  I never quite understood the fascination
> people have within adding directories almost ad-hoc into this file.
> It's potentially dangerous.

that, of course, was my main concern. 
> 
> Consider if you will that /etc/ld.so.cache contains a compiled list of
> directories that are searched for libraries and an ordered list of
> candidate libraries.  This is what the ldconfig(8) command does.  But of
> course, some people have more than one copy of libraries installed --
> and invariably this is bad.  

bad, I don't know.. but certainly awkward(?)

> Ideally, I would recommend setting LD_LIBARRY_PATH instead.

I think you mean LD_LIBRARY_PATH, am i wrong?

Sorry guys.. I couldn't resist this one.. :-)

where do I set LD_LIBRARY_PATH.. and when?

in this particular case where it's just a matter giving one application
access to a particular lib outside the /etc/ld.so.cache scheme (as
opposed to running two apps that require two different versions of the
same lib, for instance) is it something I should just set in my
~/.profile?  Or is it something I should set when I invoke ldconfig?

Apologies for the low-level questions but I'm not at all familiar with
linux system admnistration.

Thanks

cga
_______________________________________________
elinks-users mailing list
[email protected]
http://linuxfromscratch.org/mailman/listinfo/elinks-users

Reply via email to