From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 51198@debbugs.gnu.org, "Nicolò Balzarotti" <anothersms@gmail.com>
Subject: [bug#51198] [PATCH] gnu: Add b2sum.
Date: Sat, 06 Nov 2021 17:45:01 +0100 [thread overview]
Message-ID: <87o86xmdwy.fsf@gnu.org> (raw)
In-Reply-To: <YYLHs6Wx6EuaQuBR@jasmine.lan> (Leo Famulari's message of "Wed, 3 Nov 2021 13:32:35 -0400")
Hi,
Leo Famulari <leo@famulari.name> skribis:
> On Wed, Oct 27, 2021 at 05:56:31PM +0200, Ludovic Courtès wrote:
>> It’s okay but not entirely sufficient: on a cluster setup, you typically
>> talk to a daemon that’s on another machine, so the CPU features it’ll
>> detect there may be different from those you’ll use. Likewise, as
>> discussed on IRC, you’d also need #:local-build? #t.
>
> It seems that #:local-build? is not available in gnu-build-system. Is
> that correct?
Oh right, it’s missing from (guix build-system gnu). We could easily
add it.
Though again, it would remain an approximation of what we really want.
HTH!
Ludo’.
next prev parent reply other threads:[~2021-11-06 16:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 4:28 [bug#51198] [PATCH] gnu: Add b2sum Leo Famulari
2021-10-26 16:07 ` bug#51198: " Leo Famulari
2021-10-26 22:26 ` [bug#51198] " Nicolò Balzarotti
2021-10-26 22:53 ` Leo Famulari
2021-10-26 22:54 ` Leo Famulari
2021-10-26 23:16 ` Leo Famulari
2021-10-27 8:44 ` Nicolò Balzarotti
2021-10-27 15:38 ` Leo Famulari
2021-10-27 15:56 ` Ludovic Courtès
2021-11-03 17:32 ` Leo Famulari
2021-11-06 16:45 ` Ludovic Courtès [this message]
2021-11-27 23:36 ` Leo Famulari
2022-03-18 17:12 ` bug#51198: " Leo Famulari
2021-11-27 23:32 ` [bug#51198] [PATCH v2 1/2] build-system/gnu: Add #:local-build? parameter Leo Famulari
2021-11-27 23:32 ` [bug#51198] [PATCH v2 2/2] gnu: b2sum: Build on the local machine Leo Famulari
2021-12-01 15:34 ` [bug#51198] [PATCH] gnu: Add b2sum zimoun
2021-12-01 17:50 ` Leo Famulari
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=87o86xmdwy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=51198@debbugs.gnu.org \
--cc=anothersms@gmail.com \
--cc=leo@famulari.name \
/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.