From: "Gábor Boskovits" <boskovits@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Building Guile with ‘-j1’?
Date: Wed, 20 Jan 2021 11:36:28 +0100 [thread overview]
Message-ID: <CAE4v=pifZw7Ysd4khbg-3k3M18NqOttGE3ML1A8Gp-k3nSexJw@mail.gmail.com> (raw)
In-Reply-To: <87r1mgf19s.fsf@inria.fr>
Hello,
Ludovic Courtès <ludo@gnu.org> ezt írta (időpont: 2021. jan. 20., Sze, 9:42):
>
> Hi!
>
> As the saying goes, “the cobbler’s children go barefoot”. Guile/Guix
> are no exception since Guile builds are non-reproducible, despite work
> done a few years ago:
>
> https://issues.guix.gnu.org/20272
>
> Until it’s fixed in Guile proper, what do you think of building Guile
> 2.0/2.2/3.0 with #:parallel-build? #f ? We could do that in
> ‘core-updates’ now.
>
> That would work around the problem for Guile itself. It would increase
> build times, but probably not that much since the most expensive part
> (compiling the first few files) is sequential anyway. IIRC this is what
> Vagrant did for the Debian packages.
>
> We could also disable parallel builds in ‘guile-build-system’. It’s
> only used for small packages so the extra build time is probably OK.
>
> Thoughts?
Let's go for it.
>
> Ludo’.
>
Regards,
g_bor
--
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21
next prev parent reply other threads:[~2021-01-20 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 8:41 Building Guile with ‘-j1’? Ludovic Courtès
2021-01-20 10:19 ` zimoun
2021-01-20 10:36 ` Gábor Boskovits [this message]
2021-01-20 12:16 ` Jan Nieuwenhuizen
2021-01-20 21:01 ` Mark H Weaver
2021-01-21 15:17 ` Maxim Cournoyer
2021-01-28 13:35 ` Ludovic Courtès
2021-01-28 18:43 ` Maxim Cournoyer
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='CAE4v=pifZw7Ysd4khbg-3k3M18NqOttGE3ML1A8Gp-k3nSexJw@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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.