NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall in <199911192358.PAA24109@kiev.wall.org>
Did I say I expect Perl to do the right thing? :-)
--Larry Wall in <199911200217.SAA24898@kiev.wall.org>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
This is a common problem (Score:1)
This is one of the most common issues I run into when installing software where the libraries are someplace other than /usr/lib (often happens with x64 based platforms which use /usr/lib64). The best solution I've found (at least on distros that support it) is to add the library path to /etc/ld.so.conf.
Any suggestions on what to do besides LD_LIBRARY_PATH when you need to link against a library in an oddball place like /opt/custom/magicfoo/lib or something similar? I'm all ears :)
Reply to This
Re: (Score:2)
The best solution I've found (at least on distros that support it) is to add the library path to /etc/ld.so.conf
I've just discovered the document I linked to is not the same as the original. If you can hunt down the original (try Internet archive, I can't as I'm at work and it's blocked :P ), it's a must read, and it talks about ld.so.conf and why it's a bad idea. In short, what about when you need something linked against one specially compiled version of libjunk.so in /usr/local/junk and something e
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers