| 1 |
On Sunday 21 August 2005 10:56 am, Peter Bienstman wrote: |
| 2 |
> On Sunday 21 August 2005 16:33, Darren Dale wrote: |
| 3 |
> > On Sunday 21 August 2005 10:25 am, Peter Bienstman wrote: |
| 4 |
> > > On Sunday 21 August 2005 15:22, Darren Dale wrote: |
| 5 |
> > > > I use numeric and scipy, and have been trying for a long time to |
| 6 |
> > > > improve the ebuilds to use blas/lapack/atlas. I submitted an ebuild |
| 7 |
> > > > for numeric six months ago |
| 8 |
> > > > (http://bugs.gentoo.org/show_bug.cgi?id=81520), but it has languished |
| 9 |
> > > > in buzilla because it is not clear how to deal with ATLAS (my atlas |
| 10 |
> > > > USE flag was rejected). How should ATLAS dependencies be handled in |
| 11 |
> > > > the new infrastructure? |
| 12 |
> > > |
| 13 |
> > > In theory it's as simple as depending on virtual/blas and |
| 14 |
> > > virtual/lapack. The user can then switch between different lapack and |
| 15 |
> > > blas |
| 16 |
> > > implementations at runtime with blas-config and lapack-config. |
| 17 |
> > |
| 18 |
> > It is not that simple. If numeric and scipy are to make use of atlas, |
| 19 |
> > atlas has to be in their external library list at compile time. If atlas |
| 20 |
> > is in the list, but not installed on the system, compilation will fail. |
| 21 |
> |
| 22 |
> That's why I said 'in theory' ;-) |
| 23 |
> |
| 24 |
> I'm currently working on a patch which just ignores any explicit atlas |
| 25 |
> stuff at build time of SciPy. The idea is to build a library which simply |
| 26 |
> links to /usr/lib/liblapack.so. SciPy doesn't need to know this is a |
| 27 |
> symlink to /usr/lib/lapack/atlas/liblapack.so or any other implementation. |
| 28 |
|
| 29 |
If you install lapack-atlas and blas-atlas, and link scipy to the blas and |
| 30 |
lapack libraries but not the atlas libraries, do you still get the enhanced |
| 31 |
performance from atlas? (This isn't a rhetorical question, I'm still |
| 32 |
learning.) |
| 33 |
|
| 34 |
If so, great, if not, is there any point to providing the lapack-atlas and |
| 35 |
blas-atlas ebuilds? |
| 36 |
|
| 37 |
On a related topic, I noticed that sci-libs/atlas is still being developed, |
| 38 |
isn't it deprecated? This ebuild installs its libraries in /usr/lib, instead |
| 39 |
of somewhere unique and providing symlinks in /usr/lib. |
| 40 |
|
| 41 |
Darren |
| 42 |
-- |
| 43 |
gentoo-science@g.o mailing list |
Archives