From: Leo Prikler <leo.prikler@student.tugraz.at>
To: guix-devel@gnu.org
Subject: Fwd: Building Guile with ‘-j1’?
Date: Wed, 20 Jan 2021 11:46:54 +0100 [thread overview]
Message-ID: <372235f86af11b000b1dc2b493e29aca2e8706cc.camel@student.tugraz.at> (raw)
In-Reply-To: db7ce8199737fbfffaf562c6ecf152cd30d057a4.camel@student.tugraz.at
[-- Attachment #1: Type: text/plain, Size: 23 bytes --]
Messed up ML address.
[-- Attachment #2: Weitergeleitete Nachricht – Building Guile with ‘-j1’? --]
[-- Type: message/rfc822, Size: 931 bytes --]
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: ludo@gnu.org
Cc: guix-devel@debbugs.gnu.org
Subject: Building Guile with ‘-j1’?
Date: Wed, 20 Jan 2021 11:36:48 +0100
Message-ID: <db7ce8199737fbfffaf562c6ecf152cd30d057a4.camel@student.tugraz.at>
Hi Ludo,
IIUC this issue potentially affects all packages, that use Guile to
build more than two modules, no?
There could potentially be another workaround by synchronizing inside
guild, i.e. claiming a lock before reading and evaling any given source
file. This would have the advantage of applying to all guile packages,
not just the ones that use guile-build-system, and it would also allow
non-Guile stuff, e.g. C extensions to be built in parallel. WDYT?
Regards,
Leo
next parent reply other threads:[~2021-01-20 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <db7ce8199737fbfffaf562c6ecf152cd30d057a4.camel@student.tugraz.at>
2021-01-20 10:46 ` Leo Prikler [this message]
2021-01-20 21:08 ` Fwd: Building Guile with ‘-j1’? Mark H Weaver
2021-01-20 22:25 ` Leo Prikler
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=372235f86af11b000b1dc2b493e29aca2e8706cc.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=guix-devel@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).