From: gevisz <gevisz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: sci-libs/spqr-1.2.3-r1 failed to emerge
Date: Wed, 8 Apr 2020 19:31:27 +0300 [thread overview]
Message-ID: <CA+t6X7dbN1zb_nnWUp-hiqhtchvn1Wp4N3nu=shopqC4bt_52A@mail.gmail.com> (raw)
In-Reply-To: <972497a2-a3b5-dda7-422a-2029b69831f0@gentoo.org>
ср, 8 апр. 2020 г. в 18:13, Michael Orlitzky <mjo@gentoo.org>:
>
> On 4/8/20 11:01 AM, gevisz wrote:
> >
> > Unfortunately, it did not helped.
> >
>
> Before you do anything else, keyword all of the latest suitesparse
> components:
>
> ~sci-libs/suitesparseconfig-5.4.0
> ~sci-libs/amd-2.4.6
> ~sci-libs/btf-1.2.6
> ~sci-libs/camd-2.4.6
> ~sci-libs/ccolamd-2.9.6
> ~sci-libs/cholmod-3.0.13
> ~sci-libs/colamd-2.9.6
> ~sci-libs/cxsparse-3.2.0
> ~sci-libs/klu-1.3.9
> ~sci-libs/ldl-2.2.6
> ~sci-libs/spqr-2.0.9
> ~sci-libs/umfpack-5.7.9
>
> Those aren't the latest upstream releases, but at least they work, which
> is more than I can say for the stable versions.
>
> The other thing you should be aware of is that dev-lang/julia is, from a
> software engineering point of view, an absolute trainwreck (upstream,
> not the Gentoo maintainer's fault). Your experience so far is going to
> be typical, I fear.
After I added all these files to the
/etc/portage/package.accept_keywords/julia file,
julia finally emerged. Thank you. However, I am affraid what will be
when I try to
update my Gentoo system in a month or so.
next prev parent reply other threads:[~2020-04-08 16:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 10:37 [gentoo-user] sci-libs/spqr-1.2.3-r1 failed to emerge gevisz
2020-04-08 10:29 ` [gentoo-user] " Nuno Silva
2020-04-08 14:19 ` gevisz
2020-04-08 14:45 ` gevisz
2020-04-08 13:00 ` Neil Bothwick
2020-04-08 15:01 ` gevisz
2020-04-08 15:12 ` Michael Orlitzky
2020-04-08 16:31 ` gevisz [this message]
2020-04-09 6:49 ` gevisz
2020-04-09 7:32 ` Nuno Silva
2020-04-09 11:46 ` gevisz
2020-04-09 13:19 ` gevisz
2020-04-09 4:28 ` [gentoo-user] " David Haller
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='CA+t6X7dbN1zb_nnWUp-hiqhtchvn1Wp4N3nu=shopqC4bt_52A@mail.gmail.com' \
--to=gevisz@gmail.com \
--cc=gentoo-user@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