On Sunday 21 August 2005 10:56 am, Peter Bienstman wrote:
> 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.
If you install lapack-atlas and blas-atlas, and link scipy to the blas and
lapack libraries but not the atlas libraries, do you still get the enhanced
performance from atlas? (This isn't a rhetorical question, I'm still
If so, great, if not, is there any point to providing the lapack-atlas and
On a related topic, I noticed that sci-libs/atlas is still being developed,
isn't it deprecated? This ebuild installs its libraries in /usr/lib, instead
of somewhere unique and providing symlinks in /usr/lib.
email@example.com mailing list