From: "Ludovic Courtès" <ludo@gnu.org>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: 36811-close@debbugs.gnu.org
Subject: bug#36811: Guix fails to build with libgc 8.0.4
Date: Thu, 12 Mar 2020 16:59:08 +0100 [thread overview]
Message-ID: <87ftedsgxf.fsf@gnu.org> (raw)
In-Reply-To: <0e4b61bb-b593-ef47-b96c-ab3d7198a3c0@web.de> (Jonathan Brielmaier's message of "Thu, 12 Mar 2020 11:23:03 +0100")
Jonathan Brielmaier <jonathan.brielmaier@web.de> skribis:
> On 11.03.20 15:13, Ludovic Courtès wrote:> With Guile 3.0.1 + the patch for
>> <https://issues.guix.gnu.org/issue/39266>, the command above succeeds.
>>
>> Specifically:
>>
>> guix pull --commit=e4b5bdf7993590fefeb7182ae71beec4a9f69e3f
>> guix build --with-input=libgc@7=libgc@8 guile3.0-guix
>>
>> Could you confirm that it works for you?
>
> That's working for me. I built guix with guile 3.0.1 plus the patch from
> #39266 and the crash when building guix with more then two threads went
> away!
>
> Thank you, Ludovic! Closing this bug now :)
Woohoo, thanks for checking!
Ludo’.
next prev parent reply other threads:[~2020-03-12 15:59 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
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 [this message]
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=87ftedsgxf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36811-close@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).