From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Failed to set up the build environment for…
Date: Sat, 22 Mar 2014 15:17:47 +0100 [thread overview]
Message-ID: <87zjkixqpg.fsf@gnu.org> (raw)
In-Reply-To: <20140321134449.GA5037@debian> (Andreas Enge's message of "Fri, 21 Mar 2014 14:44:49 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> On Fri, Mar 21, 2014 at 01:49:59PM +0100, Ludovic Courtès wrote:
>> For now, the “solution” is to create it like this:
>> sudo mknod /dev/kvm c 10 232
>> Can you confirm?
>
> Yes, that works. Together with /dev/shm (how is this affected by the change,
> by the way?), there are more and more things to change on a debian system.
> Hopefully your patch will go through. Could /dev/kvm not simply be dropped,
> instead of enabled according to the machine on which the daemon runs? Then
> we would be closer to a deterministic build also.
We can’t simply drop it, because we want to be able to use KVM in the
build environment.
That’s a minor issue, though, because (1) the only things that rely on
KVM are the VM build support, and (2) when the stand-alone GNU exists,
it will have /dev/kvm.
Ludo’.
next prev parent reply other threads:[~2014-03-22 14:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 11:05 Failed to set up the build environment for… Alex Sassmannshausen
2014-03-19 15:46 ` Ludovic Courtès
2014-03-20 14:38 ` Andreas Enge
2014-03-20 18:07 ` Ludovic Courtès
2014-03-20 21:15 ` Andreas Enge
2014-03-20 21:40 ` Ludovic Courtès
2014-03-20 23:04 ` Alex Sassmannshausen
2014-03-21 4:04 ` Mark H Weaver
2014-03-21 12:50 ` Ludovic Courtès
2014-03-21 12:31 ` Andreas Enge
2014-03-21 12:49 ` Ludovic Courtès
2014-03-21 13:44 ` Andreas Enge
2014-03-21 15:23 ` Alex Sassmannshausen
2014-03-22 14:17 ` Ludovic Courtès [this message]
2014-03-21 15:45 ` Mark H Weaver
2014-03-21 15:59 ` Mark H Weaver
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=87zjkixqpg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--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).