From: "Ludovic Courtès" <ludo@gnu.org>
To: 40522@debbugs.gnu.org
Subject: bug#40522: ‘guile3.0-guix’ sometimes fails to build on i686 (“Too many heap sections”)
Date: Thu, 09 Apr 2020 14:04:14 +0200 [thread overview]
Message-ID: <877dyo50ht.fsf@inria.fr> (raw)
‘guile3.0-guix’ occasionally fails to build on i686-linux:
--8<---------------cut here---------------start------------->8---
[ 94%] GUILEC gnu/services/cuirass.go
[ 94%] GUILEC gnu/services/cups.go
GC Warning: Failed to expand heap by 8388608 bytes
GC Warning: Failed to expand heap by 8388608 bytes
[...]
GC Warning: Failed to expand heap by 8388608 bytes
GC Warning: Failed to expand heap by 8388608 bytes
Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
/gnu/store/7ffcr3knh5jrj3lig4qf4fv0iws51l14-bash-minimal-5.0.7/bin/bash: line 7: 28331 Aborted XDG_CACHE_HOME=/nowhere host=i686-unknown-linux-gnu srcdir="." ./pre-inst-env /gnu/store/znlp9v4z0pda450bbsfqzppqj2m61sz9-guile-next-3.0.2/bin/guile -L "." -L "." --no-auto-compile -s "."/build-aux/compile-all.scm […]
--8<---------------cut here---------------end--------------->8---
(From
<https://berlin.guixsd.org/log/czsdfjykhlc4ngjdva17i4rglpnh86fl-guile3.0-guix-1.0.1-15.0984481>.)
<https://berlin.guixsd.org/search?query=guile3.0-guix+system%3Ai686-linux>
suggests it happens only occasionally. I suspect it’s more likely when
doing ‘-j 96’ than when doing ‘-j 4’ because the former requires more
memory.
Ludo’.
next reply other threads:[~2020-04-09 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 12:04 Ludovic Courtès [this message]
2020-04-09 13:29 ` bug#40522: ‘guile3.0-guix’ sometimes fails to build on i686 (“Too many heap sections”) Danny Milosavljevic
2020-04-09 15:33 ` Ludovic Courtès
2020-10-11 14:39 ` Ludovic Courtès
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=877dyo50ht.fsf@inria.fr \
--to=ludo@gnu.org \
--cc=40522@debbugs.gnu.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).