[Python-modules-team] Bug#489726: should numpy be built with atlas?

[Ondrej Certik]

On Tue, Jul 8, 2008 at 1:58 PM, Tiziano Zito <otizonaizit at yahoo.com> wrote:
> On 7/8/08, Matthias Klose <doko at cs.tu-berlin.de> wrote:
>>  thanks for the update. Looking at the blas package, I see that the
>>  cblas library is included in libblas3.  So it looks like the numpy
>>  check is wrong, testing for a package name, and not for a
>>  feature. This seems to explain why it did work in etch, and this
>>  should be fixed in python-numpy.
>
> Hi Ondrej, Hi Matthias. Removing the two lines in numpy/core/setup.py indeed
> seems to do the trick. Feel free to test the attached patch, generated
> against the python-numpy source package in sid. On my system it
> generates a numpy package with a _dotblas.so file correctly linked to
> lapack libs. If ATLAS is then installed, the ATLAS libraries are used
> instead.
> Ondrej: if the patch works, would you report it upstream?

Yes, but first I'll upload a new package, because depending on the
atlas packages is not good.

It works on my system. Your script (attached) gives me:

$ ./test_atlas.py
Using ATLAS:
0.53141283989
$ wajig remove atlas3-base libatlas3gf-base
$ ./test_atlas.py
Using ATLAS:
1.64572000504

So it seems to work, even though the difference is not so big.

I am now going to test the package on i386 and then upload if all is
ok. We can then talk with upstream what is the best way to fix this in
the long term.

Ondrej
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test_atlas.py
Type: text/x-python
Size: 280 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20080708/fd028fe9/attachment-0001.py