From: <nunojsilva@ist.utl.pt> (Nuno Silva)
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: sci-libs/spqr-1.2.3-r1 failed to emerge
Date: Thu, 09 Apr 2020 08:32:26 +0100 [thread overview]
Message-ID: <r6mj2a$2jis$1@ciao.gmane.io> (raw)
In-Reply-To: CA+t6X7dOAQ2bDOyeN9nBQgO4uLEzCVSRFMiU_8c_dFZkMJeFyA@mail.gmail.com
On 2020-04-09, gevisz wrote:
> ср, 8 апр. 2020 г. в 19:31, gevisz <gevisz@gmail.com>:
>>
>> ср, 8 апр. 2020 г. в 18:13, Michael Orlitzky <mjo@gentoo.org>:
>> >
>> > 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.
>
> A small addition: I've just noticed that I've managed to emerge only
> julia-1.3.0;
> julia-1.4.0-r1 still fails to be emerged (at a compile phase).
What errors?
There is bug 716434[1] where julia fails because it tries to download
more tarballs (yes, during compilation). An ebuild change was made to
address this, so it might be worth syncing the tree and trying to emerge
again.
[1] https://bugs.gentoo.org/show_bug.cgi?id=716434
--
Nuno Silva
next prev parent reply other threads:[~2020-04-09 7: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
2020-04-09 6:49 ` gevisz
2020-04-09 7:32 ` Nuno Silva [this message]
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='r6mj2a$2jis$1@ciao.gmane.io' \
--to=nunojsilva@ist.utl.pt \
--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