[Numpy-discussion] Embedded NumPy LAPACK errors
Sat Jan 5 07:03:41 CST 2013
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.
I have the same problem with Enthough EPD which is built against MKL -
but I think the problem is that Intel provide two different interfaces
- ILP64 with 64 bit integer indices and LP64 with 32 bit integers.
Matlab link against the ILP64 version, whereas Enthought use the LP64
version - so there are still incompatible.
On Sat, Jan 5, 2013 at 10:42 AM, Paul Anton Letnes
> On 4. jan. 2013, at 21:42, firstname.lastname@example.org wrote:
>> 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
>> Octave, it works fine, presumably because it is compiled against
>> the same LAPACK as the NumPy I am embedding.
>> Assuming I haven't made big mistakes up to here, I have the
>> following questions:
>> Is there a way to request numpy.linalg to use a particular
>> LAPACK library, e.g. /usr/lib/liblapack.so ?
>> If not, is there a reasonable way to build numpy.linalg such that
>> it interfaces with MKL correctly ?
> It's possible, but it's much easier to install one of the pre-built python distributions. Enthought, WinPython and others include precompiled python/numpy/scipy/etc with MKL. If that works for you, I'd recommend that route, as it involves less work.
> Good luck,
> NumPy-Discussion mailing list
More information about the NumPy-Discussion