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
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.
(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.
Tuesday January 08, 2008
02:19 PM
LD_LIBRARY_PATH
I've previously linked to David Barr's fine article about LD_LIBRARY_PATH, which explains why you should never be using this variable. Unfortunately, awhile back it disappeared.
Thankfully, it has reappeared, and I thought I'd save some links to other helpful articles on the subject. It seems to finally be getting some attention.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
--Donald E. Knuth
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
not quite so (Score:2)
That's not what he said, read again. There are still legitimate uses for LD_LIBRARY_PATH (and its moral equivalents, not all platforms call it that). For example, Perl's build process uses that for a very good reason.
Re: (Score:2)
When I said "you" should never be using this variable, I meant the average person reading what I was writing. :) People who've done heavy hacking on Perl's build process have a high probability of running into the legitimate use cases for it, and I knew that. :)
Basically, if the developers of a package do their job right, and know what LD_LIBRARY_PATH is for and what it is not for, the end user should almost never, ever have to use it. If I purchase a huge commercial package like, say, Oracle, and have
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Re: (Score:2)
Re: (Score:2)
Let me also amplify that not only should a user never set LD_LIBRARY_PATH, it should never be set for him.
LD_LIBRARY_PATH is a developer-only variable. It's a test-time option, not a run-time option. Unfortunately due to many developers who don't know what they're doing, it becomes a necessary run-time option for some apps. But even then it should only be used as a method of last resort to get them running!
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Re: (Score:2)