On Tue, 9 Oct 2012, Matthieu Stigler wrote:
> Thanks Ricardo for the answer!
>
> so should I run this $sudo ldconfig in any folder? I just tried and did not
> change it., see:
> $ sudo ldconfig
> [sudo] password:
> $ gretl
> /usr/local/bin/gretl_x11: error while loading shared libraries:
> libgretl-1.0.so.4: cannot open shared object file: No such file or directory
>
> are you assuming with the ldconfig approach that the "libgretl-1.0.so.4" is
> somewhere, just badly linked? I could not even locate it on the folders...
> where is it supposed to be?
The default result of ./configure is that gretl is installed
under /usr/local: the executables in /usr/local/bin and the
library in /usr/local/lib (or /usr/local/lib64 in case of a
64-bit build).
If there's no libgretl* in /usr/local/lib or /usr/local/lib64
after "make install" then the build must have failed. In that
case, please do
make clean
make > make.log 2>&1
and we can take a look at make.log to see what happened.
If the library _did_ get installed OK but is not found by the
runtime linker, the standard fix is to run the command Jack
suggested, "sudo ldconfig". However, for this to work
/usr/local/lib (or /usr/local/lib64) must be among the
directories listed in ld.so.conf. Take a look at that file in
a text editor and if necessary, append the name of the
relevant directory (as root). For example,
sudo echo "/usr/local/lib64" >> /etc/ld.so.conf
sudo ldconfig
Allin Cottrell