On Sunday 03 April 2005 10:35, Charles Lepple wrote: > On Apr 3, 2005 8:04 AM, Stuart Brorson <[EMAIL PROTECTED]> wrote: > > As for ldconfig.cache, my Fedora machine uses a file > > "/etc/ld.so.conf". Does yours use ldconfig.cache? Which one is Linux > > standard? > > As I understand it, /etc/ld.so.conf is the standard list of > directories to search for shared libraries at runtime (in the absence > of hard-coded paths in the executable), and when you run ldconfig, it > updates /etc/ld.so.cache (which is a binary file). I haven't heard of > ldconfig.cache-- maybe that was a typo?
In fact, as I understand it, ld.so.conf is part of the Linux Standard Base. RH and other distributors claim adherence to the LSB, but this claim is dubious. For more information, refer to: http://www.faqs.org/docs/Linux-HOWTO/Program-Library-HOWTO.html The way it's supposed to work is that the list of directories on a system that are to be searched are supposed to be stored in the file /etc/ld.so.conf. A lot of Red Hat derived distributions do not include /usr/local/lib in the file /etc/ld.so.conf. Is this a bug or intentional? Regardless, it's broken. You can "fix" this by adding /usr/local/lib to /etc/ld.so.conf. The way I documentation is that ldconfig determines run-time link bindings between ld.so and shared libraries. ldconfig looks at your system and sets up the symbolic links to shared libraries. It creates /etc/ld.so.cache which is used to speed things up.
