On Tuesday 2007-05-08 20:34, Oliver Block wrote:

I compiled some servers today. Everything worked fine until I wanted to start them. Everytime when shared libraries should be loaded there was an error message saying "somelib.so: cannot open shared object file: No such file or directory"

I get that problem everytime when the share library is located in /usr/local/lib. This directory is listed in /etc/ld.so.conf. Even after calling SuSEconfig there was no improvement.

Does someone of you know the cause?

Help is appreciated.

Can you post the output of ldd yourprogramnamehere ? Did you just build/move the libraries into /usr/local/lib? Are they the same architecture of the server programs? Can you show the output of ls -l for the library files that are not loading from /usr/local/lib ? Thanks. Ken Jennings --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-programming+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-programming+help@opensuse.org

On Wed, 2007-05-09 at 17:08 +0200, Oliver Block wrote:

Somehow everythings works fine today. This has MOST LIKELY to do with a reboot. Actually I would prefer to understand why!

When this happens to me I use the "old-fashioned" ldconfig command: /sbin/ldconfig -p | grep libname (this can be done as a user) to check the ld cache has the correct entry. If the library is not found then I run "ldconfig -a" as root. If that doesn't work I would try ldd as someone else suggested. That this is fixed after reboot suggests that SuSEconfig was not running ldconfig, which is run at reboot, and so was not updating the cache. When I manually move or install things I always use ldconfig. I find SuSEconfig is designed to work with rpms and suse tools and not for manually installed software. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-programming+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-programming+help@opensuse.org