On Mon, Apr 4, 2011 at 5:48 PM, Mike Miller <mbmiller+l at gmail.com> wrote: > > I remember reading a few times that it was a bad idea to set > LD_LIBRARY_PATH in the environment and that it was best to write a script to > call the program and set LD_LIBRARY_PATH within the script. This was > probably where I read it: > LD_LIBRARY_PATH can have a lot of unintended side effects and security implications. I avoid using it if at all possible. Most binary-installs that are relocatable perform their magic by burning in max-length paths into the binaries during the initial build and then using a binary editor to replace the strings with the target paths. That setrpath tool that was mentioned was of great interest to me - there have been times I've really needed a program like that. -Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20110404/0b6ecd3c/attachment.html>