On Thu, Dec 6, 2012 at 7:35 PM, Bradley M. Froehle <[email protected]> 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. cheers, David > > > On Thu, Dec 6, 2012 at 10:34 AM, David Cournapeau <[email protected]> > wrote: >> >> On Thu, Dec 6, 2012 at 7:13 PM, Bradley M. Froehle >> <[email protected]> wrote: >> > Thanks Alexander, that was quite helpful, but unfortunately does not >> > actually work. The recommendations there are akin to a site.cfg file: >> > >> > [atlas] >> > atlas_libs = >> > library_dirs = >> > >> > [blas] >> > blas_libs = cblas,acml >> > library_dirs = /opt/acml5.2.0/gfortan64_fma4/lib >> > >> > [lapack] >> > blas_libs = cblas,acml >> > library_dirs = /opt/acml5.2.0/gfortan64_fma4/lib >> > $ python setup.py build >> > >> > However this makes numpy think that there is no optimized blas available >> > and >> > prevents the numpy.core._dotblas module from being built. >> >> _dotblas is only built if *C*blas is available (atlas, accelerate and >> mkl only are supported ATM). >> >> David >> _______________________________________________ >> NumPy-Discussion mailing list >> [email protected] >> http://mail.scipy.org/mailman/listinfo/numpy-discussion > > > > _______________________________________________ > NumPy-Discussion mailing list > [email protected] > http://mail.scipy.org/mailman/listinfo/numpy-discussion > _______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
