unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 48131@debbugs.gnu.org
Subject: bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2
Date: Mon, 03 May 2021 21:54:41 +0200	[thread overview]
Message-ID: <87fsz3wq2m.fsf@gnu.org> (raw)
In-Reply-To: <87k0ogu4wa.fsf@yucca> (Vagrant Cascadian's message of "Sun, 02 May 2021 15:50:29 -0700")

Vagrant Cascadian <vagrant@debian.org> skribis:

> On 2021-05-02, Vagrant Cascadian wrote:
>> On 2021-05-02, Ludovic Courtès wrote:

[...]

>>> Guile 3.0’s compiler with ‘-O1’ (which is what we use for package files)
>>> uses much less memory than 2.2¹.  The amount of memory may also be a
>>> function of the number of threads used (‘-j’).  So it could be that the
>>> build failed on a machine with less memory or more cores.
>>
>> The machine it failed on had 32 cores and 140GB of ram... but will
>> experiment with reducing parallelism on that machine and see if that
>> helps.
>
> I just realized that the Debian guix packages are built with parallelism
> disabled for reproducible builds, so that seems unlikely to be the
> issue... it might just be an issue with guile-2.2 on Debian...

D’oh.  Could you try reducing the number of libgc marker thread, in case
that is what’s causing troubles?  You can do that by setting the
GC_MARKERS environment variables, as in GC_MARKERS=2.

Thanks,
Ludo’.




  reply	other threads:[~2021-05-03 19:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01  0:01 bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2 Vagrant Cascadian
2021-05-02  2:17 ` Vagrant Cascadian
2021-05-02 21:59   ` Ludovic Courtès
2021-05-02 22:17     ` Vagrant Cascadian
2021-05-02 22:50       ` Vagrant Cascadian
2021-05-03 19:54         ` Ludovic Courtès [this message]
2022-03-18  2:31           ` Maxim Cournoyer
2022-03-18  6:09             ` Vagrant Cascadian

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=87fsz3wq2m.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=48131@debbugs.gnu.org \
    --cc=vagrant@debian.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).