Hi, I think I have found something. Doing exactly what I did on a 32bit machine works. But on my 64bit server, it does exactly the errors written below. Do you have a 32 or 64 machine? Oh and I don't know if the link can affect that...
$ ls -lh /usr/ [...] lrwxrwxrwx 1 root root 5 Jan 9 05:15 lib -> lib64 drwxr-xr-x 17 root root 19K Jan 11 11:05 lib32 drwxr-xr-x 102 root root 62K Jan 25 15:55 lib64 Thanks. -----Original Message----- From: Honza Machácek [mailto:[EMAIL PROTECTED] Sent: Fri 2008-01-25 15:16 To: [email protected] Subject: Re: [gentoo-science] liblapack.so.3 not found Alexandre Racine wrote: > ... > lrwxrwxrwx 1 root root 36 Jan 25 10:10 /usr/lib/liblapack.so.3 -> > /usr/lib/lapack/atlas/liblapack.so.0.0.0 > > Starting the program again, I get this: > > $ ./smartpca > ./smartpca: error while loading shared libraries: liblapack.so.3: cannot > open shared object file: No such file or directory Are you sure it does exactly that? I cannot reproduce it. Whether I link /usr/lib/liblapack.so.3 to /usr/lib/liblapack.so.0 or directly to /usr/lib/lapack/atlas/liblapack.so.0.0.0 as you did, I get libblas.so.3, not liblapack.so.3 not found. After linking /usr/lib/libblas.so.3 to /usr/lib/libblas.so.0 I start smartpca without problem: > ./smartpca ./smartpca: error while loading shared libraries: liblapack.so.3: cannot open shared object file: No such file or directory > sudo ln -s /usr/lib/liblapack.so.0 /usr/lib/liblapack.so.3 > ./smartpca ./smartpca: error while loading shared libraries: libblas.so.3: cannot open shared object file: No such file or directory > sudo ln -s /usr/lib/libblas.so.0 /usr/lib/libblas.so.3 > ./smartpca no parameters ## smartpca version: 7521 You can avoid such ugly symbolic links, if you compile the sources. With the help of `pkg-config --libs lapack` I adapted Makefile.alt to the attached Makefile.gcc4 and compiled the sources: > make -f Makefile.gcc4 all For now I don't feel like to pay those extra ten to sixty minutes to write something like a first version of an ebuild, but I thing that it might be quite straitforward. With best regards Honza Machácek
<<winmail.dat>>
