problem with lapack_lite / BLAS
Karol Langner
karol.langner at kn.pl
Sat Oct 7 14:01:47 EDT 2006
On Saturday 07 of October 2006 15:00, Karol Langner wrote:
> > > From: numpy-discussion-bounces at lists.sourceforge.net [mailto:numpy-
> > > discussion-bounces at lists.sourceforge.net] On Behalf Of Karol Langner
> > > Sent: 07 October 2006 14:07
> > > To: NumPy List
> > > Subject: [Numpy-discussion] problem with lapack_lite / BLAS
> > >
> > > Dear list,
> > >
> > > I'm trying to compile ATLAS 3.6.0 and LAPACK 3.0 (+ update) and use
> > > them with
> > > the latest numpy (checked out today). Installation seems to be fine,
> > > all the
> > > libraries are detected. When I import numpy, however, I get this:
> > >
> > > <snip>
> > > ImportError: /home/langner/apps/python/lib/python2.5/site-
> > > packages/numpy/linalg/lapack_lite.so:
> > > undefined symbol: xerbla_
> > >
> > > Does anyone know where this comes from?
OK... I am so angry at myself... I spent around 2 hours fiddling around with
blas/lapack and numpy, and the problem was that I wasn't removing the 'build'
directory between compiilations. Apparently it's not enough to run "setup.py
clean" (I read this and forgot about it) to recompile lapack_lite.so. Now
numpy imports fine and everything I use it for works as before (only a bit
faster).
Karol
P.S.
I still get a floating point exception when running the numpy tests, though. I
haven't checked out numpy for some time, so I don't now if it's a bug, or if
it's my setup. The same thing happens when I use my manually built
atlas/lapack and the built-in debian atlas/lapack libraries. I'd be grateful
for a comment on if this is just me:
>>numpy.test(10,10)
[output]
Check reading the top fields of a nested array ... ok
Check reading the nested fields of a nested array (1st level) ... ok
Check access nested descriptors of a nested array (1st level) ... ok
Check reading the nested fields of a nested array (2nd level) ... ok
Check access nested descriptors of a nested array (2nd level) ... ok
check_access_fields
(numpy.core.tests.test_numerictypes.test_read_values_plain_multiple) ... ok
check_access_fields
(numpy.core.tests.test_numerictypes.test_read_values_plain_single) ... ok
check_cdouble (numpy.tests.test_linalg.test_det)Floating point exception
thanks!
--
written by Karol Langner
Sat Oct 7 19:41:58 CEST 2006
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
More information about the NumPy-Discussion
mailing list