From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Building Guile with ‘-j1’?
Date: Thu, 28 Jan 2021 13:43:43 -0500 [thread overview]
Message-ID: <87wnvwyk9s.fsf@gmail.com> (raw)
In-Reply-To: <87sg6lnq0j.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 28 Jan 2021 14:35:08 +0100")
Hi,
Ludovic Courtès <ludo@gnu.org> writes:
> Hi Maxim,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
>> Mark H Weaver <mhw@netris.org> writes:
>>
>>> Hi Ludovic,
>>>
>>> Ludovic Courtès <ludo@gnu.org> writes:
>>>
>>>> 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.
>
> I pushed that as 2ea52f90141974fb5d88b8c6b1785817c4203da4.
>
>> I'm not too found of it. It'll make the already slow Guile build much
>> slower, making the lower strata of core-updates packages more painfully
>> slow to build and test.
>
> Yes, it’s suboptimal. OTOH, as I wrote, I think the slowdown is not as
> important as one might think: a large fraction of the Guile build time
> goes into building ice-9/eval.scm and the first few files, which is
> already sequential (enforced by Guile’s makefile).
I've built Guile many times on core-updates since and it seems to be
true, that the build time didn't change noticeably.
>> It'll also enable us to overlook the issue for years to come
>> (similarly to the fact that the testsuite of the Guix package itself
>> hasn't been run in parallel for the last 6 years or so :-)).
>
> It remains and bug to fix in Guile, no doubt. But we also have to be
> pragmatic IMO.
I had the feeling this partial fix would cause build the build time to
explode, but given it didn't, I'm happy with it.
Thanks,
Maxim
prev parent reply other threads:[~2021-01-28 18:44 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
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 [this message]
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=87wnvwyk9s.fsf@gmail.com \
--to=maxim.cournoyer@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 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).