31.3.2011 19:05, Kai Ruottu kirjoitti:
31.3.2011 17:16, Mahmood Naderan kirjoitti:
/opt/gcc4.6build/./gcc/cc1: error while loading shared libraries:
libmpc.so.2:
cannot open shared object file: No such file or directory
It complains about libmpc.so.2 however I have this file since I
installed MPC from source:
root@pc:/opt/gcc4.6build# ls -l /usr/local/lib/libmpc.*
-rw-r--r-- 1 root root 147256 2011-03-31 12:37 /usr/local/lib/libmpc.a
-rwxr-xr-x 1 root root 946 2011-03-31 12:37 /usr/local/lib/libmpc.la
lrwxrwxrwx 1 root root 15 2011-03-31 12:37 /usr/local/lib/libmpc.so ->
libmpc.so.2.0.0
lrwxrwxrwx 1 root root 15 2011-03-31 12:37 /usr/local/lib/libmpc.so.2 ->
libmpc.so.2.0.0
-rwxr-xr-x 1 root root 89558 2011-03-31 12:37
/usr/local/lib/libmpc.so.2.0.0
As you can see in the config.log, I configured the gcc to install in
/usr. What should I do in order to tell gcc where is libmpc.so.2 ?
Aren't there any "linux-help" list for questions like this?
Let's add some expected logic (common sense) into this issue :
- when someone wants to add new shared libraries, new tools etc
from sources into the "Linux system", one configures their
sources using '--prefix=/usr'
- if one doesn't want the "original system" being mixed with one's
own local additions, then the default '--prefix=/usr/local' is
one good choice. But one must take the local additions in
'/usr/local/bin' and '/usr/local/lib' in use via modifying PATH
and something else for the shared libraries, like adding a new
'.conf' text file into the '/etc/ld.so.conf.d'. For instance my
system has :
[root@localhost etc]# cat ld.so.conf.d/*.conf
/usr/lib/mysql
/opt/meego/lib
/usr/lib/qt-3.3/lib
/usr/lib/xulrunner-1.9.2
Maybe the previous isn't the "official truth", but hopefully it
is at least a little near it...
