ld.so.conf and cache problems

Forum: myDSL Extensions (deprecated)
Topic: ld.so.conf and cache problems
started by: clacker

Posted by clacker on Nov. 30 2004,20:22

In order to install r-recommended using apt-get, I had to delete the link from /etc/ld.so.cache to /KNOPPIX/etc/ld.so.cache and replace it with a copy of that file. That let the program install and it worked fine.

I've been trying to make a dsl package, but I've run into a snag: if I put ld.so.cache and ld.so.conf into the dsl, everything works but I'm overwriting what the user had before (bad). If I don't include ld.so.cache and conf in the package, the program can't find its libraries.

Is there a way to get around this? Is there any way to view ld.so.cache so I can see where it puts the file virtually so that I can put the real file there?

Posted by cbagger01 on Nov. 30 2004,23:27

If the program is having trouble finding it's libraries, maybe you can leave those two files alone and write a shell wrapper that contains an export LD_LIBRARY_PATH statement that tells the program where these libraries are located.

It might not work, but it's worth a try.

Posted by aesenadorjr on Feb. 25 2005,06:01

I was just reading this wiki entry from linuxquestions.org about ldconfig.

< http://wiki.linuxquestions.org/wiki/Library-related_Commands_and_Files >

I would like to paraphrase the entry on ldconfig for my own benefit. It says that if new dynamic library files are added in the directory tree, just edit the ld.so.conf to add the paths to the library files and then run ldconfig. This will search through all the paths listed in ld.so.conf, create the necessary symlinks, and update the ld.so.cache.

Now, if I may use the newly-found knowledge to this thread, the file ld.so.cache should never be touched directly by any loading of dsl extensions. First inspect the contents of the ld.so.conf inside his prospective .dsl package and compare it with that of /KNOPPIX/etc/ld.so.conf. If they match, remove the one inside the .dsl package. If they do not match, ensure that the new ld.so.conf also contains everything in the old one (edit if necessary) and include it in the .dsl package. Either way, whoever loads that .dsl package must be alerted to run ldconfig after loading.

If I am still correct so far, then I would like to solicit opinions about revising the /etc/init.d/mydsl-install script such that changes to the ld.so.conf will be detected and will cause ldconfig to run. This can be applicable only to .dsl extensions.

OK, now I want to know my grade on this one...