From: "Bastian Löffler" <Bastian_Loeffler@arcor.de>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] Build of cxvopt against acml not working
Date: Mon, 13 Jan 2014 23:49:10 +0100 [thread overview]
Message-ID: <52D46D66.10809@arcor.de> (raw)
In-Reply-To: <52D46D28.6070707@arcor.de>
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
Am 13.01.2014 23:43, schrieb François Bissey:
> On 2014-01-14 11:05, Bastian Löffler wrote:
>> Hi all,
>>
> ........
>>
>> Strange: libacml.so live in /usr/lib and /usr/lib64 .... Ideas?
>
> What does /usr/lib64/libacml.so points to? Since acml is a binary
> package it shouldn't live
> in /usr/lib{64} but somewhere in /opt. My guess is that you are not
> using acml from the science
> overlay. I am not even sure you have it from the main tree.
>
> Francois
>
>
>
next parent reply other threads:[~2014-01-13 22:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52D46D28.6070707@arcor.de>
2014-01-13 22:49 ` Bastian Löffler [this message]
2014-01-13 22:58 ` [gentoo-science] Build of cxvopt against acml not working François Bissey
2014-01-13 23:12 ` Bastian Löffler
2014-01-13 23:18 ` François Bissey
2014-01-13 23:30 ` Bastian Löffler
2014-01-13 23:41 ` François Bissey
2014-01-14 0:09 ` François Bissey
2014-01-15 10:08 ` François Bissey
[not found] <52D45FFD.4090104@yahoo.de>
2014-01-13 22:05 ` Bastian Löffler
2014-01-13 22:43 ` François Bissey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52D46D66.10809@arcor.de \
--to=bastian_loeffler@arcor.de \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox