I think that blas/lapack/atlas support in portage has several inconsistencies. For example, there are three packages related to atlas sci-libs/atlas sci-libs/blas-atlas sci-libs/lapack-atlas However. sci-libs/atlas does not provide blas neither lapack. And if I emerge, blas-atlas and then lapack-atlas, I have to compile atlas twice!. This is quit frustrating, since Atlas takes a lot of time to compile. The most reasonable thing would be to have just one sci-libs/atlas package and that this package provides both virtual/blas and virtual/lapack. Another inconsistency is that we have both sci-libs/blas and sci-libs/blas-reference in portage. blas reference provides virtual/blas but blas does not! So I emerge blas, and it does not provide blas! (what seems rather absurd to me) (and what it is worst, the strange behavior of all this packages seems not to be documented anywhere)
I second these comments. The lapack/blas/atlas packages are all fairly confusing.
Here's the deal: blas-{atlas,reference} and lapack-{atlas,reference} are new. blas and lapack are old. We've been waiting around for the new stuff to get stable and get good testing so we can remove the old stuff.
*** Bug 119396 has been marked as a duplicate of this bug. ***
(In reply to comment #2) > Here's the deal: > blas-{atlas,reference} and lapack-{atlas,reference} are new. > > blas and lapack are old. > > We've been waiting around for the new stuff to get stable and get good testing > so we can remove the old stuff. > This bug is approaching one year old. I'd say atlas 3-7-3x is in excellent shape on amd64 and x86 in both the lapack and blas versions. I've got a few scattered instances of packages outside of Portage that depend on them not being able to find them at link time, but other than that atlas seems to be as stable as it could be. Are we waiting for upstream to formally release 3.8.0??
We're currently in the process of moving to new-style virtuals for blas and lapack so we can do away with all the provide stuff and hopefully then make the *-reference ebuilds the default instead of the much "heavier" *-atlas ones.
Sounds good ... I actually have all five blas and all three lapack packages on my systems. My machines are all AMD, so I have the ACML library installed. My personal default is ACML for lapack and threaded Atlas for blas, though.
blas and lapack implementations are now hopefully now more consistent.
