[SciPy-user] tracebacks when running tests
Elliot Peele
ebpeele2 at pams.ncsu.edu
Thu Jun 3 01:49:43 EDT 2004
When I run the tests I get tracebacks which reference scipy.linalg.eig.
I wrote a simple test case to test this, but I get the following
traceback.
>>> import scipy.linalg
>>> eig = scipy.linalg.eig
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/lib/python2.2/site-packages/scipy_base/ppimport.py", line
303, in __getattr__
module = self._ppimport_importer()
File "/usr/lib/python2.2/site-packages/scipy_base/ppimport.py", line
273, in _ppimport_importer
module = __import__(name,None,None,['*'])
File "/usr/lib/python2.2/site-packages/scipy/linalg/__init__.py", line
8, in ? from basic import *
File "/usr/lib/python2.2/site-packages/scipy/linalg/basic.py", line
11, in ?
from lapack import get_lapack_funcs
File "/usr/lib/python2.2/site-packages/scipy/linalg/lapack.py", line
16, in ?
import clapack
ImportError: /usr/lib/python2.2/site-packages/scipy/linalg/clapack.so:
undefined symbol: clapack_sgesv
Looking at the ldd output for clapack.so:
[elliot at rkbuild linalg]$ ldd clapack.so
liblapack.so.3 => /usr/lib/liblapack.so.3 (0xb6eb4000)
libg2c.so.0 => /usr/lib/libg2c.so.0 (0xb6e96000)
libm.so.6 => /lib/tls/libm.so.6 (0xb6e74000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb6e6a000)
libc.so.6 => /lib/tls/libc.so.6 (0xb6d32000)
libblas.so.3 => /usr/lib/libblas.so.3 (0xb6ce2000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
It links against liblapack.so.3 which doesn't include the symbols that
were added from atlas since they are in liblapack.a. Is there anyway to
fix this?
Elliot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://mail.scipy.org/pipermail/scipy-user/attachments/20040603/1ff999b5/attachment.sig>
More information about the SciPy-User
mailing list