[Numpy-discussion] site.cfg: Custom BLAS / LAPACK configuration
Dag Sverre Seljebotn
Fri Dec 7 12:58:26 CST 2012
One way of fixing this I'm sort of itching to do is to create a
"pylapack" project which can iterate quickly on these build issues,
run-time selection of LAPACK backend and so on. (With some templates
generating some Cython code it shouldn't be more than a few days for an
Then patch NumPy to attempt to import pylapack (and if it's there, get a
table of function pointers from it).
The idea would be that powerusers could more easily build pylapack the
way they wanted, in isolation, and then have other things switch to that
without a rebuild (note again that it would need to export a table of
But I'm itching to do too many things, we'll see.
On 12/07/2012 07:09 PM, Bradley M. Froehle wrote:
> Aha, thanks for the clarification. I've always been surpassed that NumPy doesn't ship with a copy of CBLAS. It's easy to compile --- just a thin wrapper over BLAS, if I remember correctly.
> On Friday, December 7, 2012 at 4:01 AM, David Cournapeau wrote:
>> On Thu, Dec 6, 2012 at 7:35 PM, Bradley M. Froehle
>> <email@example.com (mailto:firstname.lastname@example.org)> wrote:
>>> Right, but if I link to libcblas, cblas would be available, no?
>> No, because we don't explicitly check for CBLAS. We assume it is there
>> if Atlas, Accelerate or MKL is found.
> NumPy-Discussion mailing list
More information about the NumPy-Discussion