1 |
> Here are my logs. You'll find some warnings in the configuration |
2 |
> stage, I hope they'll mean something to you. Also, there's no trace of |
3 |
> libclapack.so in |
4 |
> ldd /usr/lib64/python2.7/site-packages/scipy/linalg/clapack.so. |
5 |
|
6 |
The output of ldd /usr/lib64/python2.7/site-packages/scipy/linalg/clapack.so |
7 |
is very suspicious with Atlas it should look like this: |
8 |
ldd /usr/lib/python2.7/site-packages/scipy/linalg/clapack.so |
9 |
linux-gate.so.1 => (0xb7890000) |
10 |
liblapack.so.0 => /usr/lib/liblapack.so.0 (0xb732a000) |
11 |
libpython2.7.so.1.0 => /usr/lib/libpython2.7.so.1.0 (0xb71bb000) |
12 |
libc.so.6 => /lib/libc.so.6 (0xb7035000) |
13 |
libblas.so.0 => /usr/lib/blas/atlas/libblas.so.0 (0xb7014000) |
14 |
libcblas.so.0 => /usr/lib/blas/atlas/libcblas.so.0 (0xb6ff2000) |
15 |
libatlas.so.0 => /usr/lib/libatlas.so.0 (0xb6933000) |
16 |
libgfortran.so.3 => /usr/lib/gcc/i686-pc-linux- |
17 |
gnu/4.5.2/libgfortran.so.3 (0xb6871000) |
18 |
libm.so.6 => /lib/libm.so.6 (0xb684b000) |
19 |
libgcc_s.so.1 => /usr/lib/gcc/i686-pc-linux-gnu/4.5.2/libgcc_s.so.1 |
20 |
(0xb682d000) |
21 |
libpthread.so.0 => /lib/libpthread.so.0 (0xb6813000) |
22 |
libdl.so.2 => /lib/libdl.so.2 (0xb680f000) |
23 |
libutil.so.1 => /lib/libutil.so.1 (0xb680b000) |
24 |
/lib/ld-linux.so.2 (0xb7891000) |
25 |
|
26 |
So nothing from blas/cblas/lapack was linked into your scipy which is very |
27 |
worrying. It may be that there is a problem with your current blas&co setup. |
28 |
what's the output of |
29 |
ls -la /usr/lib64/libcblas.so |
30 |
|
31 |
Francois |