Stories
Slash Boxes
Comments
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

use Perl Log In

Log In

[ Create a new account ]

jdavidb (1361)

jdavidb
  (email not shown publicly)
http://voiceofjohn.blogspot.com/

J. David Blackstone has a Bachelor of Science in Computer Science and Engineering and nine years of experience at a wireless telecommunications company, where he learned Perl and never looked back. J. David has an advantage in that he works really hard, he has a passion for writing good software, and he knows many of the world's best Perl programmers.

Journal of jdavidb (1361)

Friday September 29, 2006
04:23 PM

Compiling software and the dynamic loader path

[ #31166 ]

One of the most annoying things to me in installing many pieces of software, including many Perl modules, is that often the maintainers seem to not understand the concepts expressed here (here until recently ... what in the world happened?). Usually, there is no readily apparent means of setting LD_RUN_PATH and/or -R options in the compilation path, although often the software authors are happy to tell you that you'll probably need to set LD_LIBRARY_PATH in order to get their software to run.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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 :)

    • 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