[Numpy-discussion] 64-bit windows numpy / scipy wheels for testing

[Matthew Brett]

Hi,

On Thu, May 8, 2014 at 5:51 PM, Matthew Brett <matthew.brett at gmail.com> wrote:
> Hi,
>
> On Mon, Apr 28, 2014 at 3:29 PM, David Cournapeau <cournape at gmail.com> wrote:
>>
>>
>>
>> On Sun, Apr 27, 2014 at 11:50 PM, Matthew Brett <matthew.brett at gmail.com>
>> wrote:
>>>
>>> Aha,
>>>
>>> On Sun, Apr 27, 2014 at 3:19 PM, Matthew Brett <matthew.brett at gmail.com>
>>> wrote:
>>> > Hi,
>>> >
>>> > On Sun, Apr 27, 2014 at 3:06 PM, Carl Kleffner <cmkleffner at gmail.com>
>>> > wrote:
>>> >> A possible option is to install the toolchain inside site-packages and
>>> >> to
>>> >> deploy it as PYPI wheel or wininst packages. The PATH to the toolchain
>>> >> could
>>> >> be extended during import of the package. But I have no idea, whats the
>>> >> best
>>> >> strategy to additionaly install ATLAS or other third party libraries.
>>> >
>>> > Maybe we could provide ATLAS binaries for 32 / 64 bit as part of the
>>> > devkit package.  It sounds like OpenBLAS will be much easier to build,
>>> > so we could start with ATLAS binaries as a default, expecting OpenBLAS
>>> > to be built more often with the toolchain.  I think that's how numpy
>>> > binary installers are built at the moment - using old binary builds of
>>> > ATLAS.
>>> >
>>> > I'm happy to provide the builds of ATLAS - e.g. here:
>>> >
>>> > https://nipy.bic.berkeley.edu/scipy_installers/atlas_builds
>>>
>>> I just found the official numpy binary builds of ATLAS:
>>>
>>> https://github.com/numpy/vendor/tree/master/binaries
>>>
>>> But - they are from an old version of ATLAS / Lapack, and only for 32-bit.
>>>
>>> David - what say we update these to latest ATLAS stable?
>>
>>
>> Fine by me (not that you need my approval !).
>>
>> How easy is it to build ATLAS targetting a specific CPU these days ? I think
>> we need to at least support nosse and sse2 and above.
>
> I'm getting crashes trying to build SSE2-only ATLAS on 32-bits, I
> think Clint will have some time to help out next week.

Clint spent an hour on the phone working through the 32-bit build.
There was a nasty gcc bug revealed by some oddness to the input flags.
 Fixed now:

https://nipy.bic.berkeley.edu/scipy_installers/atlas_builds/

Configure flags needed for 32-bit:

config_opts="-b 32 -Si archdef 0 -A 13 -V 384 \
    --with-netlib-lapack-tarfile=${lapack_tarfile} \
    -Fa al '-mincoming-stack-boundary=2 -mfpmath=sse -msse2'"

For 64-bit:

config_opts="-b 64 -V 384 --with-netlib-lapack-tarfile=${lapack_tarfile}"

Cheers,

Matthew