[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

why is ldconfig needed after installation

From: Peter Johansson
Subject: why is ldconfig needed after installation
Date: Mon, 26 May 2014 10:53:06 +1000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130108 Thunderbird/10.0.12

Hi libtoolers,

I just installed a library with libtool (via automake generated rules) and when trying to use the lib I get this:

error while loading shared libraries:

which is going away if I issue

sudo ldconfig /us/local/lib

My question is why is that even needed, as I thought libtool already did that. No?

I've noticed the message at installation
Libraries have been installed in:

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and manual pages.

So I've followed the last bit there and added a file '/etc/' that contains '/usr/local/lib' to make the runtime linker aware of '/usr/local/lib'. Yet I need to do a ldconfig manually every time I install something. Am I missing something or doing something wrong? This is on RHEL6.


This is on RHEL6 and I've added

Peter Johansson

reply via email to

[Prev in Thread] Current Thread [Next in Thread]