From: "François Bissey" <frp.bissey@gmail.com>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] .la files harmful to BLAS/LAPACK structure
Date: Thu, 22 Oct 2020 19:28:32 +1300 [thread overview]
Message-ID: <EAAFB32F-C95B-44EE-8FAE-7FC50CC3567B@gmail.com> (raw)
In-Reply-To: <D8AAE507-A839-473E-AA47-29113B8CC65E@gmail.com>
> On 22/10/2020, at 11:21 AM, François Bissey <frp.bissey@gmail.com> wrote:
>
> * All the suitesparse ebuilds - that are not explicitly multibuild (messes up glpk).
> * All the coinor ebuilds - probably with the same exceptions for mutlibuild.
> * dev-libs/igraph (0.7.1-r2 at least, concerning as it links to blas/lapack)
> * libsemigroup [sage-on-gentoo]
> * gap [sage-on-gentoo]
> * sci-libs/iml (concerning since it links to cblas)
> * sys-cluster/mpich
> * dev-libs/libltdl
* sci-mathematics/gmp-ecm
prev parent reply other threads:[~2020-10-22 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 22:21 [gentoo-science] .la files harmful to BLAS/LAPACK structure François Bissey
2020-10-22 0:23 ` Aisha Tammy
2020-10-22 0:43 ` François Bissey
2020-10-22 6:28 ` François Bissey [this message]
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=EAAFB32F-C95B-44EE-8FAE-7FC50CC3567B@gmail.com \
--to=frp.bissey@gmail.com \
--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