From: Andy Wingo <wingo@igalia.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Preliminary IceCat 68.2 package
Date: Wed, 23 Oct 2019 15:18:32 +0200 [thread overview]
Message-ID: <87v9sfk3br.fsf@igalia.com> (raw)
In-Reply-To: <87blu7zr8f.fsf@netris.org> (Mark H. Weaver's message of "Wed, 23 Oct 2019 06:32:37 -0400")
Heya Mark :)
On Wed 23 Oct 2019 12:32, Mark H Weaver <mhw@netris.org> writes:
> I wrote:
>> * Many earlier attempts to build it have failed due to non-deterministic
>> failures in the build system, possibly due to a bug in the Cargo tool.
>> I'm not sure how much luck was involved in my successful build. Your
>> mileage may vary.
>
> Having now done a few more test builds, I'm sorry to say that the build
> seems to often fail non-deterministically. Most of my attempts have
> failed so far.
>
> The most common failure mode is described in these bug reports for
> Gentoo and BLFS:
>
> https://bugs.gentoo.org/show_bug.cgi?id=680934
> http://wiki.linuxfromscratch.org/blfs/ticket/11975#comment:6
>
> Those errors, where a backtrace is printed by cargo, happen at a
> different place in the build every time. If you're lucky, you might get
> through the entire build without hitting that bug.
>
> I'd be very grateful for help debugging these failures or finding a
> workaround.
I don't know what this is, but at work I have to build Firefox a lot,
and sometimes the rust bits die in the middle of compilation. Is it a
resource exhaustion issue? I am not sure. In any case, continuing to
"make" always solves it for me. I know that's not very reassuring, but
if you're looking for a quick workaround, running your "make -jN" in a
loop 5 times or something may be good enough.
Cheers,
Andy
next prev parent reply other threads:[~2019-10-23 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 8:37 Preliminary IceCat 68.2 package Mark H Weaver
2019-10-23 10:32 ` Mark H Weaver
2019-10-23 13:18 ` Andy Wingo [this message]
2019-10-23 15:06 ` Mark H Weaver
2019-10-23 19:50 ` Mark H Weaver
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9sfk3br.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).