Что плохого при создании gcc 4.9.1?

Question

В пакете новейший GCC 4.9.1, после ./configure я побежал делать, и он потерпел неудачу с сообщением об ошибке:

checking for x86_64-unknown-linux-gnu-gcc... /root/tar/gcc-4.9.1/host-x86_64-unknown-linux-gnu/gcc/xgcc -B/root/tar/gcc-4.9.1/host-x86_64-unknown-linux-gnu/gcc/ -B/usr/local/x86_64-unknown-linux-gnu/bin/ -B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem /usr/local/x86_64-unknown-linux-gnu/include -isystem /usr/local/x86_64-unknown-linux-gnu/sys-include 
checking for suffix of object files... configure: error: in `/root/tar/gcc-4.9.1/x86_64-unknown-linux-gnu/libgcc': 
configure: error: cannot compute suffix of object files: cannot compile 
See `config.log' for more details. 

Я проверил config.log в x86_64-неизвестно-линукс-ГНУ/libgcc /, и он сказал:

configure:3389: /root/tar/gcc-4.9.1/host-x86_64-unknown-linux-gnu/gcc/xgcc -B/root/tar/gcc-4.9.1/host-x86_64-unknown-linux-gnu/gcc/ -B/usr/local/x86_64-unknown-linux-gnu/bin/ -B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem /usr/local/x86_64-unknown-linux-gnu/include -isystem /usr/local/x86_64-unknown-linux-gnu/sys-include -o conftest -g -O2 conftest.c >&5 
/root/tar/gcc-4.9.1/host-x86_64-unknown-linux-gnu/gcc/cc1: error while loading shared libraries: libmpc.so.2: cannot open shared object file: No such file or directory 
configure:3392: $? = 1 
configure:3580: checking for suffix of object files 
configure:3602: /root/tar/gcc-4.9.1/host-x86_64-unknown-linux-gnu/gcc/xgcc -B/root/tar/gcc-4.9.1/host-x86_64-unknown-linux-gnu/gcc/ -B/usr/local/x86_64-unknown-linux-gnu/bin/ -B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem /usr/local/x86_64-unknown-linux-gnu/include -isystem /usr/local/x86_64-unknown-linux-gnu/sys-include -c -g -O2 conftest.c >&5 
/root/tar/gcc-4.9.1/host-x86_64-unknown-linux-gnu/gcc/cc1: error while loading shared libraries: libmpc.so.2: cannot open shared object file: No such file or directory 
configure:3606: $? = 1 
configure: failed program was: 

Но, очевидно, у меня есть libmpc.so.2 in/usr/local/lib. Что не так??

Answer 1

Похоже, проблема связана с тем, что путь по умолчанию/usr/local/lib не включен в переменную среды $ LD_LIBRARY_PATH. Извините за этот глупый вопрос ...