Sun, 25 Jan 2009 10:44:15 -0500, Gideon Simpson wrote:
> Rebuilding the library against ATLAS 3.8.2 with lapack 3.1.1 seems to
> have done the trick. I do get one failure:
>
> ==
> FAIL: test_umath.TestComplexFunctions.test_agai
Rebuilding the library against ATLAS 3.8.2 with lapack 3.1.1 seems to
have done the trick. I do get one failure:
==
FAIL: test_umath.TestComplexFunctions.test_against_cmath
--
David Cournapeau wrote:
> Hoyt Koepke wrote:
> Actually, I would advise using only 3.8.2. Previous versions had bugs
> for some core routines used by numpy (at least 3.8.0 did). I am a bit
> surprised that a 64 bits-built atlas would be runnable at all in a 32
> bits binary - I would expect the
Gideon Simpson wrote:
> Rerunning the tests with verbosity, it dies at:
>
> test_single (test_linalg.TestSolve) ... ok
> Ticket #652 ... *** glibc detected *** python: free(): invalid next
> size (fast): 0x01e284e0 ***
>
> I'm using ATLAS 3.8.2 and lapack 3.2.
>
Lapack 3.2 may be the
Rerunning the tests with verbosity, it dies at:
test_single (test_linalg.TestSolve) ... ok
Ticket #652 ... *** glibc detected *** python: free(): invalid next
size (fast): 0x01e284e0 ***
I'm using ATLAS 3.8.2 and lapack 3.2. ATLAS and lapack were all built
with the -m64 flag.
-gideon
Hoyt Koepke wrote:
> Not sure what the problem is in your case, but I had the same error a
> while back. For some reason, ATLAS thought it should be compiled as
> 64 bit but numpy as 32 bit. . It went away after I passed the -b 32
> flag to configure in ATLAS (I think). Thus that's one thing to
Not sure what the problem is in your case, but I had the same error a
while back. For some reason, ATLAS thought it should be compiled as
64 bit but numpy as 32 bit. . It went away after I passed the -b 32
flag to configure in ATLAS (I think). Thus that's one thing to check.
Also, make sure you'
On Sat, Jan 24, 2009 at 22:47, Gideon Simpson wrote:
> Having built an up to date lapack and ATLAS against gcc 4.3.2, I tried
> installing numpy 1.2.1 on Python 2.5.4. When testing I get:
Run numpy.test(verbose=2) in order to have nose print out the name of
the method it is running before actual
Gideon Simpson wrote:
> Having built an up to date lapack and ATLAS against gcc 4.3.2, I tried
> installing numpy 1.2.1 on Python 2.5.4. When testing I get:
>
> Python 2.5.4 (r254:67916, Jan 24 2009, 00:27:20)
> [GCC 4.3.2] on linux2
> Type "help", "copyright", "credits" or "license" for more in
Having built an up to date lapack and ATLAS against gcc 4.3.2, I tried
installing numpy 1.2.1 on Python 2.5.4. When testing I get:
Python 2.5.4 (r254:67916, Jan 24 2009, 00:27:20)
[GCC 4.3.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
>>>
10 matches
Mail list logo
