64bit or not ?

[Kevin Davidson]

>
>    You might be able to make 'em go by setting LD_LIBRARY_PATH to
> /lib32:/usr/lib:/usr/local/lib  (or whatever other places it needs to
> find libraries) before running the binary.  Not a guarantee,  
> especially
> if the app had hardwired paths and tried to do it's own dynamic  
> loading
> of libs, but...


In a previous life as a software engineer I came to regard  
LD_LIBRARY_PATH as an evil, insidious, virus-like mis-feature. If you  
really must use it , do so as a point-fix: create a shell script  
wrapper around problem binaries. Never, ever, ever set LD_LIBRARY_PATH  
in your .profile .tcshrc or similar. Never. Ever. Especially if you  
are compiling packages from source or you will infect them with the  
requirement that LD_LIBRARY_PATH be similarly set when THEY are run.  
You can then expect other things to start breaking. This used to be a  
real issue for Sun's OpenWindows which had X11 libraries installed in / 
usr/openwin instead of /usr/X11 - many sites used to routinely set  
LD_LIBRARY_PATH in the skeleton .tcshrc causing all sorts of mayhem  
and heartache. LD_RUN_PATH is a fix only in the same sense that  
airbags are a fix for faulty brakes in a car.

Kevin Davidson
Technical Director

t 0870 745 4001
m 07813 149620
w www.indigospring.co.uk



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20080123/606ffb65/attachment-0001.htm