From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: Christopher Baines <mail@cbaines.net>, guix-devel@gnu.org
Subject: Re: Implications of QEMU binfmt transparent emulation for builds
Date: Sun, 07 Mar 2021 00:19:44 +0100 [thread overview]
Message-ID: <0de60501672d88b8014d2adb9b617c7576d40714.camel@zaclys.net> (raw)
In-Reply-To: <87eegsnexv.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
On Sat, 2021-03-06 at 21:35 +0000, Christopher Baines wrote:
In general I think binary translation is very wasteful use of computing
resources. At least use something like this:
http://csl.iis.sinica.edu.tw/hqemu/ - otherwise I think building
natively is at the end less costly.
> I'd like the Guix Build Coordinator agents to be able to report the
> configuration of the machine at the time builds happen, so maybe once
> that's a feature, and QEMU support can be detected, then it'll be
> possible to look for cases where a change in QEMU support affects the
> build result.
What about including such metadata in Nars directly? Kernel name and
version string, system/target, processor model.. or is that too
privacy-invasive..? Maybe make such opt-in.
Léo
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-06 23:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 21:35 Implications of QEMU binfmt transparent emulation for builds Christopher Baines
2021-03-06 23:19 ` Léo Le Bouter [this message]
2021-03-07 11:44 ` Christopher Baines
2021-03-07 1:34 ` Mark H Weaver
2021-03-07 12:00 ` Christopher Baines
2021-04-21 3:29 ` Maxim Cournoyer
2021-03-10 10:47 ` Ludovic Courtès
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=0de60501672d88b8014d2adb9b617c7576d40714.camel@zaclys.net \
--to=lle-bout@zaclys.net \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
/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.