all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: 36811@debbugs.gnu.org, bug-guix@gnu.org
Subject: bug#36811: Guix fails to build with libgc 8.0.4
Date: Mon, 18 Nov 2019 15:13:06 +0100	[thread overview]
Message-ID: <87o8x9i87h.fsf@gnu.org> (raw)
In-Reply-To: <154d15a4-2851-6cc3-16b1-b020e27e02e9@web.de> (Jonathan Brielmaier's message of "Thu, 25 Jul 2019 20:26:15 +0200")

Hi Jonathan,

Jonathan Brielmaier <jonathan.brielmaier@web.de> skribis:

> Guix fails to build on Tumbleweed with `make -j4` or a greater thread
> count (see guile_coredump_building_guix.log)
>
> It doesn't fail to build with `make -j3` or less threads and when
> building inside of `guix environment --pure guix`.
>
> I then started to look around what could differ between Tumbleweed and
> guix environment. My first assumption was kind of hit :)
>
> Tumbleweed is built since some days with libgc 8.0.4 and Guix is still
> on 7.6.6. In my home project[0] I have built now Guix (and Guile) with
> libgc 7.6.4, the version Tumbleweed used before. Guix builds now with
> `make -j4` and greater again on Tumbleweed...
>
> So it seems that guile is not compatible with libgc 8.x yet? Is this
> correct?

To isolate the problem, how about:

  1. Defining a Guix package for libgc 8.0.4;

  2. Running “guix build guile --with-input=libgc@7=libgc@8” (or
     defining a package along these lines).

?

Thanks in advance,
Ludo’.

  reply	other threads:[~2019-11-18 14:13 UTC|newest]

Thread overview: 3+ 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 [this message]
2019-11-19 12:09   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o8x9i87h.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=36811@debbugs.gnu.org \
    --cc=bug-guix@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.