Re: [Numpy-discussion] successful Windows x64 build with acml-5.3.1 ifort64 static libs passes tests

2014-10-23 Thread Mark Mikofski
AMD acml libraries do not include the CBLAS implementation. To build CBLAS against the libacml.lib requires the Intel Fortran compiler. There is a note in the mailing list here http://mail.scipy.org/pipermail/numpy-discussion/2006-February/018379.html This detail should probably be added to

Re: [Numpy-discussion] successful Windows x64 build with acml-5.3.1 ifort64 static libs passes tests

2014-10-23 Thread Mark Mikofski
I am so dumb. It is not using the static libs at all. It is building numpy with lapack_lite and blas_lite. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] successful Windows x64 build with acml-5.3.1 ifort64 static libs passes tests

2014-10-23 Thread Mark Mikofski
Both the /MT and /MD versions of the acml static libraries build, and pass all tests, except that for me at least there's a weird glitch in the build process. I have to purposefully add something so that config fails. EG: In the previous site.cfg, I did not realize that I had mistyped the vector

Re: [Numpy-discussion] segfault in np.arange

2014-10-23 Thread Julian Taylor
On 23.10.2014 19:21, Dave Hirschfeld wrote: > Hi, > I accidentally passed a pandas DatetimeIndex to `np.arange` which caused > it to segfault. It's a pretty dumb thing to do but I don't think it > should cause a segfault! thanks for the report, this patch should fix it: https://github.com/nump

[Numpy-discussion] segfault in np.arange

2014-10-23 Thread Dave Hirschfeld
Hi, I accidentally passed a pandas DatetimeIndex to `np.arange` which caused it to segfault. It's a pretty dumb thing to do but I don't think it should cause a segfault! Python 2.7.5 |Continuum Analytics, Inc.| (default, Jul 1 2013, 12:37:52) [MSC v.1500 64 bit (AMD64)] on win32 Type "help",