Well ....

I found that the link was wrong (old version) it was pointing to
nowhere. I removed it. Now i have no link in /usr/lib{64} anymore:

file /opt/acml5.3.1/gfortran64/lib/libacml.so
/opt/acml5.3.1/gfortran64/lib/libacml.so: ELF 64-bit LSB shared object,
x86-64, version 1 (SYSV), dynamically linked, not stripped

pkg-config lapack --libs
-L//opt/acml5.3.1/gfortran64/lib -lacml

And yes eselect shows acml.


Am 13.01.2014 23:58, schrieb François Bissey:
> On 2014-01-14 11:49, Bastian Löffler wrote:
>> Hi
>>
>> ls -la /usr/lib64/ | grep libacml.so
>> lrwxrwxrwx   1 root root       40 19. Mai 2013  libacml.so ->
>> /opt/acml5.3.0/gfortran64/lib/libacml.so
>>
>> It is from the science overlay it does not exist in the main tree:
>>  emerge -av acml
>>
>> These are the packages that would be merged, in order:
>>
>> Calculating dependencies... done!
>> [ebuild   Rf   ] sci-libs/acml-5.3.1::science  USE="doc examples
>> gfortran openmp -fma -ifort -int64 -open64 -pgi -static-libs {-test}"
>> 0 kB
>>
>>
> OK I just find it bizarre that there is a link in /usr/lib64, I don't
> have it installed
> myself. So I am guessing
> eselect blas list
> will show acml as being selected and
> eselect lapack list
> will show the same.
> Is
> file /opt/acml5.3.0/gfortran64/lib/libacml.so
> reporting a 64bit shared object as it should?
> And finally what does
> pkg-config lapack --libs
> says?
>
> Francois
>
>


Reply via email to