| 1 |
Hi |
| 2 |
|
| 3 |
ls -la /usr/lib64/ | grep libacml.so |
| 4 |
lrwxrwxrwx 1 root root 40 19. Mai 2013 libacml.so -> |
| 5 |
/opt/acml5.3.0/gfortran64/lib/libacml.so |
| 6 |
|
| 7 |
It is from the science overlay it does not exist in the main tree: |
| 8 |
emerge -av acml |
| 9 |
|
| 10 |
These are the packages that would be merged, in order: |
| 11 |
|
| 12 |
Calculating dependencies... done! |
| 13 |
[ebuild Rf ] sci-libs/acml-5.3.1::science USE="doc examples |
| 14 |
gfortran openmp -fma -ifort -int64 -open64 -pgi -static-libs {-test}" 0 kB |
| 15 |
|
| 16 |
|
| 17 |
Am 13.01.2014 23:43, schrieb François Bissey: |
| 18 |
> On 2014-01-14 11:05, Bastian Löffler wrote: |
| 19 |
>> Hi all, |
| 20 |
>> |
| 21 |
> ........ |
| 22 |
>> |
| 23 |
>> Strange: libacml.so live in /usr/lib and /usr/lib64 .... Ideas? |
| 24 |
> |
| 25 |
> What does /usr/lib64/libacml.so points to? Since acml is a binary |
| 26 |
> package it shouldn't live |
| 27 |
> in /usr/lib{64} but somewhere in /opt. My guess is that you are not |
| 28 |
> using acml from the science |
| 29 |
> overlay. I am not even sure you have it from the main tree. |
| 30 |
> |
| 31 |
> Francois |
| 32 |
> |
| 33 |
> |
| 34 |
> |
Archives