| 1 |
On 2014-01-14 11:49, Bastian Löffler wrote: |
| 2 |
> Hi |
| 3 |
> |
| 4 |
> ls -la /usr/lib64/ | grep libacml.so |
| 5 |
> lrwxrwxrwx 1 root root 40 19. Mai 2013 libacml.so -> |
| 6 |
> /opt/acml5.3.0/gfortran64/lib/libacml.so |
| 7 |
> |
| 8 |
> It is from the science overlay it does not exist in the main tree: |
| 9 |
> emerge -av acml |
| 10 |
> |
| 11 |
> These are the packages that would be merged, in order: |
| 12 |
> |
| 13 |
> Calculating dependencies... done! |
| 14 |
> [ebuild Rf ] sci-libs/acml-5.3.1::science USE="doc examples |
| 15 |
> gfortran openmp -fma -ifort -int64 -open64 -pgi -static-libs {-test}" 0 |
| 16 |
> kB |
| 17 |
> |
| 18 |
> |
| 19 |
OK I just find it bizarre that there is a link in /usr/lib64, I don't |
| 20 |
have it installed |
| 21 |
myself. So I am guessing |
| 22 |
eselect blas list |
| 23 |
will show acml as being selected and |
| 24 |
eselect lapack list |
| 25 |
will show the same. |
| 26 |
Is |
| 27 |
file /opt/acml5.3.0/gfortran64/lib/libacml.so |
| 28 |
reporting a 64bit shared object as it should? |
| 29 |
And finally what does |
| 30 |
pkg-config lapack --libs |
| 31 |
says? |
| 32 |
|
| 33 |
Francois |
Archives