From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Building Guile with ‘-j1’?
Date: Thu, 21 Jan 2021 10:17:25 -0500 [thread overview]
Message-ID: <87im7qfhfe.fsf@gmail.com> (raw)
In-Reply-To: <877do7gw4i.fsf@netris.org> (Mark H. Weaver's message of "Wed, 20 Jan 2021 16:01:54 -0500")
Hi,
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'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. 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 also won't fix the issue of Guix modules compiled in parallel
suffering from the same problem.
So I'd keep it as it is for now, as a reminder that this is a serious
problem in need of a fix.
Thanks,
Maxim
next prev parent reply other threads:[~2021-01-21 15:18 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 [this message]
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=87im7qfhfe.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.