[Numpy-discussion] ** On entry to ILAENV parameter number 2 had an illegal value
Fri Jul 31 23:15:51 CDT 2009
On Sat, Aug 1, 2009 at 1:14 PM, David Cournapeau<firstname.lastname@example.org> wrote:
> On Fri, Jul 31, 2009 at 8:20 PM, David
> Cournapeau<email@example.com> wrote:
>> Steven Coutts wrote:
>>> David Cournapeau <david <at> ar.media.kyoto-u.ac.jp> writes:
>>> If you are willing to do
>>>> it, I would also be interested whether numpy works ok if linked against
>>>> BLAS/LAPACK instead of atlas (i.e. build numpy, again from scratch, with
>>>> ATLAS=None python setup.py build, and then run the test suite).
>>> Yes that appears to work fine, all tests run.
>> So that's a problem with ATLAS. Maybe a gcc bug ? Another user contacted
>> me privately for my rpm repository, and got exactly the same problem
>> with the rpms, on CENTOS 5.3 as well. I will try to look at it on a
>> centos VM if I have time this WE,
> Ok, I have installed CENTOS 5.3 on my machine (kudos to vmware fusion
> which installs the OS automatically), build numpy 1.3.0 with atlas
> 3.8.3 + lapack 3.1.1 on 64 bits. But I could not reproduce the bug,
> unfortunately. Are you using the threaded atlas ?
I forgot: another thing which would be helpful since you can reproduce
the bug would be to build a debug version of numpy (python setup.py
build_ext -g), and reproduce the bug under gdb to have a traceback.
More information about the NumPy-Discussion