| 1 |
Hi Jody, |
| 2 |
|
| 3 |
The mechanism for handling multiple BLAS/LAPACK in the science overlay |
| 4 |
is incompatible with the one used in the main tree. |
| 5 |
In particular the science overlay stack doesn't create link link to |
| 6 |
libcblas, |
| 7 |
libblas and liblapack. |
| 8 |
You have to unmask eselect from the science overlay as well as the |
| 9 |
virtuals |
| 10 |
(cblas,blas and lapack) and remove all the tree eselect-blas, |
| 11 |
eselect-cblas |
| 12 |
and eselect-lapack modules. |
| 13 |
No packages in Gentoo, in the tree or the overlay, should use libblas, |
| 14 |
libcblas or |
| 15 |
liblapack directly but configure it throught pkg-config. |
| 16 |
All BLAS/LAPACK implementation in Gentoo provide .pc file for that |
| 17 |
purpose. With |
| 18 |
the new science overlay structure you create a link for which .pc file |
| 19 |
is the default. |
| 20 |
|
| 21 |
So once you have completed your move to the science overlay stack you |
| 22 |
need to remove |
| 23 |
those links if they still exist. |
| 24 |
|
| 25 |
Francois |
| 26 |
|
| 27 |
On 2013-09-02 19:04, jody wrote: |
| 28 |
> Hi |
| 29 |
> I have successfully installed sci-libs/atlas from the science overlay. |
| 30 |
> |
| 31 |
> Now there are some points which are somewhat unclear. |
| 32 |
> |
| 33 |
> I have been redirected here from the gentoo forum. |
| 34 |
> |
| 35 |
> 1. cblas implementation |
| 36 |
> Even though |
| 37 |
> |
| 38 |
> # eselect cblas list |
| 39 |
> Available providers for cblas: |
| 40 |
> [1] atlas * |
| 41 |
> [2] atlas-threads |
| 42 |
> |
| 43 |
> all cblas libraries are pointing to gsl implementations: |
| 44 |
> |
| 45 |
> ls -l /usr/lib64/libcblas.* |
| 46 |
> lrwxrwxrwx 1 root root 13 Aug 20 10:54 /usr/lib64/libcblas.a -> |
| 47 |
> libgslcblas.a |
| 48 |
> lrwxrwxrwx 1 root root 14 Aug 20 10:54 /usr/lib64/libcblas.so -> |
| 49 |
> libgslcblas.so |
| 50 |
> lrwxrwxrwx 1 root root 16 Aug 20 10:54 /usr/lib64/libcblas.so.0 -> |
| 51 |
> libgslcblas.so.0 |
| 52 |
> |
| 53 |
> Shouldn't the '/usr/lib64/libcblas.so' point to |
| 54 |
> '/usr/lib64/libatlcblas.so' etc.? |
| 55 |
> |
| 56 |
> 2. static libs for cblas |
| 57 |
> The installation of sci-libs/atlas did not create any static libs: |
| 58 |
> |
| 59 |
> ls -l /usr/lib64/libatl* |
| 60 |
> lrwxrwxrwx 1 root root 13 Aug 22 09:11 /usr/lib64/libatlas.so |
| 61 |
> -> libatlas.so.3 |
| 62 |
> -rwxr-xr-x 1 root root 5961968 Aug 22 09:11 /usr/lib64/libatlas.so.3 |
| 63 |
> lrwxrwxrwx 1 root root 16 Aug 22 09:11 |
| 64 |
> /usr/lib64/libatlcblas.so -> libatlcblas.so.3 |
| 65 |
> -rwxr-xr-x 1 root root 142504 Aug 22 09:11 |
| 66 |
> /usr/lib64/libatlcblas.so.3 |
| 67 |
> |
| 68 |
> And i have at least one 3rd party code which requires the cblas |
| 69 |
> libraries to be linked statically. |
| 70 |
> |
| 71 |
> 3. eselect lapack |
| 72 |
> I found that 'app-admin/eselect-lapack' is blocking 'sci-libs/atlas', |
| 73 |
> |
| 74 |
> but atlas did not pull in eselect for lapack: |
| 75 |
> |
| 76 |
> # eselect lapack list |
| 77 |
> !!! Error: Can't load module lapack |
| 78 |
> exiting |
| 79 |
> |
| 80 |
> eselect-cblas is also blocking 'sci-libs/atlas', but apparently atlas |
| 81 |
> pulls in eselect for cblas. |
| 82 |
> |
| 83 |
> 4. Shouldn't there also be a lapack implementation from atlas? |
| 84 |
> |
| 85 |
> Could somebody clarify or help out? |
| 86 |
> Jody |
Archives