> oops. It is ATLAS. I was able to run with a nonoptimized lapack.
Just to confirm, it also works for me when I use Netlib BLAS instead
of ATLAS.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/num
Mathew Yeates wrote:
> my set up is similar. Same cpu's. Except I am using atlas 3.9.1 and gcc
> 4.2.4
>
ATLAS 3.9.1 is a development version, and is not supposed to be used for
production use. Please use 3.8.2 if you want to build your own atlas,
cheers,
David
__
> This smells like an ATLAS problem. You should seed a note to Clint
> Whaley (the ATLAS guy). IIRC, ATLAS has some hand coded asm routines and
> it seems that support for these very new processors might be broken.
I believe the machine is a couple of years old, though it's a
fairly high-end wo
On Tue, Jul 29, 2008 at 18:00, Mathew Yeates <[EMAIL PROTECTED]> wrote:
> What got fixed?
>>>(look at the second one, warnings wasn't imported?)
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret
What got fixed?
Robert Kern wrote:
> On Tue, Jul 29, 2008 at 17:41, Mathew Yeates <[EMAIL PROTECTED]> wrote:
>
>> Charles R Harris wrote:
>>
>>> This smells like an ATLAS problem.
>>>
>> I don't think so. I crash in a call to dsyevd which part of lapack but
>> not atlas. Also, when
On Tue, Jul 29, 2008 at 17:41, Mathew Yeates <[EMAIL PROTECTED]> wrote:
> Charles R Harris wrote:
>>
>>
>> This smells like an ATLAS problem.
> I don't think so. I crash in a call to dsyevd which part of lapack but
> not atlas. Also, when I commented out the call to test_eigh_build I get
> zillions
oops. It is ATLAS. I was able to run with a nonoptimized lapack.
Mathew Yeates wrote:
> Charles R Harris wrote:
>
>> This smells like an ATLAS problem.
>>
> I don't think so. I crash in a call to dsyevd which part of lapack but
> not atlas. Also, when I commented out the call to test_eigh
Charles R Harris wrote:
>
>
> This smells like an ATLAS problem.
I don't think so. I crash in a call to dsyevd which part of lapack but
not atlas. Also, when I commented out the call to test_eigh_build I get
zillions of errors like (look at the second one, warnings wasn't imported?)
=
On Tue, Jul 29, 2008 at 2:48 PM, James Turner <[EMAIL PROTECTED]> wrote:
> Thanks everyone. I think I might try using the Netlib BLAS, since
> it's a server installation... but please let me know if you'd like
> me to troubleshoot this some more (the sooner the easier).
>
This smells like an ATLA
more info
when /linalg.py(872)eigh() calls dsyevd I crash
James Turner wrote:
> Thanks everyone. I think I might try using the Netlib BLAS, since
> it's a server installation... but please let me know if you'd like
> me to troubleshoot this some more (the sooner the easier).
>
> James.
>
> ___
Thanks everyone. I think I might try using the Netlib BLAS, since
it's a server installation... but please let me know if you'd like
me to troubleshoot this some more (the sooner the easier).
James.
___
Numpy-discussion mailing list
Numpy-discussion@sci
I am using an ATLAS 64 bit lapack 3.9.1.
My cpu (4 cpus)
-
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU X5460 @ 3.16GHz
stepping: 6
cpu MHz
my set up is similar. Same cpu's. Except I am using atlas 3.9.1 and gcc
4.2.4
James Turner wrote:
>> Are you using ATLAS? If so, where did you get it and what cpu do you have?
>>
>
> Yes. I have Atlas 3.8.2. I think I got it from
> http://math-atlas.sourceforge.net. I also included Lapack 3.
> Are you using ATLAS? If so, where did you get it and what cpu do you have?
Yes. I have Atlas 3.8.2. I think I got it from
http://math-atlas.sourceforge.net. I also included Lapack 3.1.1
from Netlib when building it from source. This worked on another
machine.
According to /proc/cpuinfo, I have
Thanks, Robert.
> Can you do
>
> numpy.test(verbosity=2)
OK. Here is the line that fails:
check_matvec (numpy.core.tests.test_numeric.TestDot)Floating exception (core
dumped)
> A gdb backtrace would also help.
OK. I'm pretty ignorant about using debuggers, but I did
"gdb python core.23696" a
On Tue, Jul 29, 2008 at 1:16 PM, James Turner <[EMAIL PROTECTED]> wrote:
> I have built NumPy 1.1.0 on RedHat Enterprise 3 (Linux 2.4.21
> with gcc 3.2.3 and glibc 2.3.2) and Python 2.5.1. When I run
> numpy.test() I get a core dump, as follows. I haven't noticed
> any special errors during the bu
I'm getting this too
Ticket #652 ... ok
Ticket 662.Segmentation fault
Robert Kern wrote:
> On Tue, Jul 29, 2008 at 14:16, James Turner <[EMAIL PROTECTED]> wrote:
>
>> I have built NumPy 1.1.0 on RedHat Enterprise 3 (Linux 2.4.21
>> with gcc 3.2.3 and glibc 2.3.2) and Python 2.5.1. When I run
>
On Tue, Jul 29, 2008 at 14:16, James Turner <[EMAIL PROTECTED]> wrote:
> I have built NumPy 1.1.0 on RedHat Enterprise 3 (Linux 2.4.21
> with gcc 3.2.3 and glibc 2.3.2) and Python 2.5.1. When I run
> numpy.test() I get a core dump, as follows. I haven't noticed
> any special errors during the build
I have built NumPy 1.1.0 on RedHat Enterprise 3 (Linux 2.4.21
with gcc 3.2.3 and glibc 2.3.2) and Python 2.5.1. When I run
numpy.test() I get a core dump, as follows. I haven't noticed
any special errors during the build. Should I post the entire
terminal output from "python setup.py install"? Mayb
19 matches
Mail list logo
