Re: [Numpy-discussion] Embedded NumPy LAPACK errors

2013-01-08 Thread Robin
On Sat, Jan 5, 2013 at 1:03 PM, Robin wrote: >>> If not, is there a reasonable way to build numpy.linalg such that >>> it interfaces with MKL correctly ? I managed to get this to work in the end. Since Matlab uses MKL with ILP64 interface it is not possible to get Numpy to use that without modifi

Re: [Numpy-discussion] Embedded NumPy LAPACK errors

2013-01-05 Thread Robin
Coincidently I have been having the same problem this week. Unrelated to the problem, I would suggest looking at pymex which 'wraps' python inside Matlab very nicely, although it has the same problem with duplicate lapack symbols. https://github.com/kw/pymex I have the same problem with Enthough

Re: [Numpy-discussion] Embedded NumPy LAPACK errors

2013-01-05 Thread Paul Anton Letnes
On 4. jan. 2013, at 21:42, m...@eml.cc wrote: > Hiall, > > > I am trying to embed numerical code in a mexFunction, > as called by MATLAB, written as a Cython function. > > NumPy core functions and BLAS work fine, but calls to LAPACK > function such as SVD seem to be made against to MATLAB's li

[Numpy-discussion] Embedded NumPy LAPACK errors

2013-01-04 Thread m...@eml.cc
Hiall, I am trying to embed numerical code in a mexFunction, as called by MATLAB, written as a Cython function. NumPy core functions and BLAS work fine, but calls to LAPACK function such as SVD seem to be made against to MATLAB's linked MKL, and this generates MKL errors. When I try this with Oc