From: "Ludovic Courtès" <ludo@gnu.org>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: 36811@debbugs.gnu.org
Subject: bug#36811: Guix fails to build with libgc 8.0.4
Date: Thu, 06 Feb 2020 15:07:41 +0100 [thread overview]
Message-ID: <877e0z95ci.fsf@gnu.org> (raw)
In-Reply-To: <6b263a31-01d5-634d-54f1-e2f04018bdc8@web.de> (Jonathan Brielmaier's message of "Wed, 20 Nov 2019 17:06:19 +0100")
Hi Jonathan,
As discussed yesterday on #guix, I tried this:
guix build guile3.0-guix --with-input=libgc@7=libgc@8
as of Guix commit 9d0dfd9a9a7c43363a4e140c20d49f119fe6f2e3. Guile 3.0.0
itself builds fine (test suite included), but the build of Guix crashes
like this (on x86_64-linux-gnu):
--8<---------------cut here---------------start------------->8---
[ 76%] GUILEC gnu/packages/icu4c.go
[ 77%] GUILEC gnu/packages/idris.go
[ 77%] GUILEC gnu/packages/idutils.go
[ 77%] GUILEC gnu/packages/image.go
[ 77%] GUILEC gnu/packages/image-processing.go
[ 77%] GUILEC gnu/packages/image-viewers.go
mmap(PROT_NONE) failed
/gnu/store/29jhbbg1hf557x8j53f9sxd9imlmf02a-bash-minimal-5.0.7/bin/bash: line 7: 26886 Aborted XDG_CACH
E_HOME=/nowhere host=x86_64-unknown-linux-gnu srcdir="." ./pre-inst-env /gnu/store/dcsjagbjlhjj40g30lb88wx3zybmh07g-gui
le-next-3.0.0/bin/guile -L "." -L "." --no-auto-compile -s "."/build-aux/compile-all.scm guix/base16.scm guix/base32.sc
m guix/base64.scm guix/ci.scm guix/cpio.scm guix/deprecation.scm guix/docker.scm guix/json.scm guix/records.scm guix/pk
--8<---------------cut here---------------end--------------->8---
Apparently the message and abort come from ‘GC_unmap’ or ‘GC_unmap_gap’
in libgc, but I have no idea what to think about it. Could it be a heap
exhaustion issue or similar? That’s not impossible.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-02-06 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 18:26 bug#36811: Guix fails to build with libgc 8.0.4 Jonathan Brielmaier
2019-11-18 14:13 ` Ludovic Courtès
2019-11-19 12:09 ` Jonathan Brielmaier
2019-11-19 13:33 ` Jonathan Brielmaier
2019-11-20 14:09 ` Ludovic Courtès
2019-11-20 14:16 ` Jonathan Brielmaier
2019-11-20 15:39 ` Ludovic Courtès
2019-11-20 16:06 ` Jonathan Brielmaier
2020-02-06 14:07 ` Ludovic Courtès [this message]
2020-02-06 14:16 ` Jonathan Brielmaier
2020-03-11 14:13 ` Ludovic Courtès
2020-03-12 10:23 ` Jonathan Brielmaier
2020-03-12 15:59 ` Ludovic Courtès
2020-03-12 16:15 ` Jonathan Brielmaier
2020-02-03 11:49 ` Jonathan Brielmaier
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877e0z95ci.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36811@debbugs.gnu.org \
--cc=jonathan.brielmaier@web.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).