From: ludo@gnu.org (Ludovic Courtès)
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Offloading to a VM
Date: Mon, 29 Aug 2016 14:54:02 +0200 [thread overview]
Message-ID: <87r3974txx.fsf@gnu.org> (raw)
In-Reply-To: <CAL1_im=vJ37Xne4+BGYg012ELa4FMK4NrmzwfJowJGNfBTwkdw@mail.gmail.com> (David Craven's message of "Sun, 28 Aug 2016 16:38:59 +0200")
David Craven <david@craven.ch> skribis:
>> --8<---------------cut here---------------start------------->8---
>> $ qemu-arm $(guix build coreutils -s armhf-linux |grep -v debug)/bin/uname -a
>> Linux pluto 4.7.0-gnu #1 SMP 1 armv7l GNU/Linux
>> $ uname -a
>> Linux pluto 4.7.0-gnu #1 SMP 1 x86_64 GNU/Linux
>> --8<---------------cut here---------------end--------------->8---
>
> If I understand correctly this only works when there is a substitute
> already. If it's a new package for example that would fail with "not
> an armhf system" right?
The “build hook” is the mechanism by which the daemon asks an external
program whether it can build a derivation for some system.
Our (guix scripts offload) is such a program; it replies positively if
there’s a machine that matches the target system.
What I was suggesting is to have another build hook that would reply
positively as long as the target system can be emulated by QEMU.
Does that makes sense?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-08-29 12:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 7:50 Build machine sysadmin support Ludovic Courtès
2016-08-21 12:42 ` David Craven
2016-08-21 14:34 ` David Craven
2016-08-21 17:38 ` David Craven
2016-08-27 10:31 ` David Craven
2016-08-28 14:30 ` Offloading to a VM Ludovic Courtès
2016-08-28 14:38 ` David Craven
2016-08-29 12:54 ` Ludovic Courtès [this message]
2016-08-29 12:56 ` David Craven
2016-09-03 14:27 ` David Craven
2016-09-03 14:32 ` David Craven
2016-09-05 20:30 ` Ludovic Courtès
2016-09-05 20:50 ` David Craven
2016-09-05 20:28 ` Ludovic Courtès
2016-08-28 14:22 ` ‘guix system vm’ and shared store Ludovic Courtès
2016-08-28 14:33 ` Build machine sysadmin support 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
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=87r3974txx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=david@craven.ch \
--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).