David, how do these environment variables compare with yours? Are you sure
MKL is being used?
Adjusted for your local path, what does the ldd command below show?
ldd /usr/local/lib/python2.5/site-packages/numpy/linalg/lapack_lite.so
linux-gate.so.1 => (0xffffe000)
libmkl_lapack.so => /opt/intel/mkl/
10.0.3.020/lib/32/libmkl_lapack.so (0xb7ae4000)
/opt/intel/mkl/10.0.3.020/lib/32/libmkl_intel.so (0xb79a6000)
/opt/intel/mkl/10.0.3.020/lib/32/libmkl_intel_thread.so (0xb77a9000)
/opt/intel/mkl/10.0.3.020/lib/32/libmkl_core.so (0xb7745000)
libguide.so => /opt/intel/mkl/10.0.3.020/lib/32/libguide.so(0xb76e3000)
libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb76b7000)
libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7586000)
libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb7582000)
/lib/ld-linux.so.2 (0x80000000)
Relevant lines from .bashrc:
source /opt/intel/cc/10.1.015/bin/iccvars.sh
source /opt/intel/fc/10.1.015/bin/ifortvars.sh
source /opt/intel/mkl/10.0.3.020/tools/environment/mklvars32.sh
export PYTHONPATH=/usr/local/lib/python2.5/site-packages:/usr/lib/python2.5
The above statements set relevant environment variables:
CPATH=/opt/intel/mkl/10.0.3.020/include
FPATH=/opt/intel/mkl/10.0.3.020/include
DYLD_LIBRARY_PATH=/opt/intel/fc/10.1.015/lib:/opt/intel/cc/10.1.015/lib
INCLUDE=/opt/intel/mkl/10.0.3.020/include
LD_LIBRARY_PATH=/opt/intel/mkl/
10.0.3.020/lib/32:/opt/intel/fc/10.1.015/lib:/opt/intel/cc/10.1.015/lib
LIBRARY_PATH=/opt/intel/mkl/10.0.3.020/lib/32
MANPATH=/opt/intel/mkl/
10.0.3.020/man:/opt/intel/fc/10.1.015/man:/opt/intel/cc/10.1.015/m
an:/opt/intel/cc/10.1.015/man:/usr/local/man:/usr/local/share/man:/usr/share/man
MKLROOT=/opt/intel/mkl/10.0.3.020
PYTHONPATH=/usr/local/lib/python2.5/site-packages:/usr/lib/python2.5
Are we having fun yet? :(
_______________________________________________
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
