On Wed, Mar 11, 2009 at 1:34 PM, Francesc Alted <fal...@pytables.org> wrote:
> A Wednesday 11 March 2009, Ryan May escrigué: > > Hi, > > > > I noticed the following in numpy/distutils/system_info.py while > > trying to get numpy to build against MKL: > > > > if cpu.is_Itanium(): > > plt = '64' > > #l = 'mkl_ipf' > > elif cpu.is_Xeon(): > > plt = 'em64t' > > #l = 'mkl_em64t' > > else: > > plt = '32' > > #l = 'mkl_ia32' > > > > So in the autodetection for MKL, the only way to get plt (platform) > > set to 'em64t' is to test true for a Xeon. This function returns > > false on my Core2 Duo system, even though the platform is very much > > 'em64t'. I think that check should instead read: > > > > elif cpu.is_Xeon() or cpu.is_Core2(): > > > > Thoughts? > > This may help you to see the developer's view on this subject: > > http://projects.scipy.org/numpy/ticket/994 > > Cheers, > > -- > Francesc Alted > _______________________________________________ > Numpy-discussion mailing list > Numpy-discussion@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion > You know, I knew this sounded familiar. If you regularly build against MKL, can you send me your site.cfg. I've had a lot more success getting the build to work using the autodetection than the blas_opt and lapack_opt sections. Since the autodetection doesn't seem like the accepted way, I'd love to see how to get the accepted way to actually work. :) Ryan -- Ryan May Graduate Research Assistant School of Meteorology University of Oklahoma Sent from: Norman Oklahoma United States.
_______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
