EL Sat, 4 Jun 2011 12:15:18 +1200 Francois Bissey <[email protected]> escrigué:
> > Here are my logs. You'll find some warnings in the configuration > > stage, I hope they'll mean something to you. Also, there's no trace > > of libclapack.so in > > ldd /usr/lib64/python2.7/site-packages/scipy/linalg/clapack.so. > > The output of > ldd /usr/lib64/python2.7/site-packages/scipy/linalg/clapack.so is > very suspicious with Atlas it should look like this: > ldd /usr/lib/python2.7/site-packages/scipy/linalg/clapack.so > linux-gate.so.1 => (0xb7890000) liblapack.so.0 > => /usr/lib/liblapack.so.0 (0xb732a000) libpython2.7.so.1.0 > => /usr/lib/libpython2.7.so.1.0 (0xb71bb000) libc.so.6 > => /lib/libc.so.6 (0xb7035000) libblas.so.0 > => /usr/lib/blas/atlas/libblas.so.0 (0xb7014000) libcblas.so.0 > => /usr/lib/blas/atlas/libcblas.so.0 (0xb6ff2000) libatlas.so.0 > => /usr/lib/libatlas.so.0 (0xb6933000) libgfortran.so.3 > => /usr/lib/gcc/i686-pc-linux- gnu/4.5.2/libgfortran.so.3 (0xb6871000) > libm.so.6 => /lib/libm.so.6 (0xb684b000) > libgcc_s.so.1 > => /usr/lib/gcc/i686-pc-linux-gnu/4.5.2/libgcc_s.so.1 (0xb682d000) > libpthread.so.0 => /lib/libpthread.so.0 (0xb6813000) > libdl.so.2 => /lib/libdl.so.2 (0xb680f000) > libutil.so.1 => /lib/libutil.so.1 (0xb680b000) > /lib/ld-linux.so.2 (0xb7891000) > > So nothing from blas/cblas/lapack was linked into your scipy which is > very worrying. It may be that there is a problem with your current > blas&co setup. what's the output of > ls -la /usr/lib64/libcblas.so > > Francois > ls -la /usr/lib64/libcblas.so lrwxrwxrwx 1 root root 26 2 jun 13:44 /usr/lib64/libcblas.so -> blas/reference/libcblas.so ls -la /usr/lib64/libblas.so lrwxrwxrwx 1 root root 25 2 jun 13:43 /usr/lib64/libblas.so -> blas/reference/libblas.so ls -la /usr/lib64/liblapack.so lrwxrwxrwx 1 root root 29 2 jun 13:47 /usr/lib64/liblapack.so -> lapack/reference/liblapack.so It looks reasonable to me.
signature.asc
Description: PGP signature
