From: Jan Nieuwenhuizen <janneke@gnu.org>
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 13:16:39 +0100 [thread overview]
Message-ID: <87y2gnrefs.fsf@gnu.org> (raw)
In-Reply-To: <87r1mgf19s.fsf@inria.fr> ("Ludovic Courtès"'s message of "Wed, 20 Jan 2021 09:41:51 +0100")
Ludovic Courtès writes:
Hello,
> 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
Ugh. Thanks for bringing this up again. Would you consider disabling
parallel builds in Guile by default, adding something like a
"--enable-somewhat-faster-non-reproducible-build" configure option until
this is fixed?
> 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.
Yes, I would support at least doing this.
> 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.
Are packages using guile-build-system expected to build non-reproducible
too? In that case, I would certainly support doing it there.
Greetings,
Janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2021-01-20 12:17 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
2021-01-20 12:16 ` Jan Nieuwenhuizen [this message]
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
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=87y2gnrefs.fsf@gnu.org \
--to=janneke@gnu.org \
--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 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).