On Sunday 21 August 2005 16:33, Darren Dale wrote: > On Sunday 21 August 2005 10:25 am, Peter Bienstman wrote: > > On Sunday 21 August 2005 15:22, Darren Dale wrote: > > > I use numeric and scipy, and have been trying for a long time to > > > improve the ebuilds to use blas/lapack/atlas. I submitted an ebuild for > > > numeric six months ago (http://bugs.gentoo.org/show_bug.cgi?id=81520), > > > but it has languished in buzilla because it is not clear how to deal > > > with ATLAS (my atlas USE flag was rejected). How should ATLAS > > > dependencies be handled in the new infrastructure? > > > > In theory it's as simple as depending on virtual/blas and virtual/lapack. > > The user can then switch between different lapack and blas > > implementations at runtime with blas-config and lapack-config. > > It is not that simple. If numeric and scipy are to make use of atlas, atlas > has to be in their external library list at compile time. If atlas is in > the list, but not installed on the system, compilation will fail.
That's why I said 'in theory' ;-) I'm currently working on a patch which just ignores any explicit atlas stuff at build time of SciPy. The idea is to build a library which simply links to /usr/lib/liblapack.so. SciPy doesn't need to know this is a symlink to /usr/lib/lapack/atlas/liblapack.so or any other implementation. Peter
pgpGNWfHlULqq.pgp
Description: PGP signature
