From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Failed to set up the build environment for…
Date: Fri, 21 Mar 2014 11:59:07 -0400 [thread overview]
Message-ID: <87y503mtkk.fsf@yeeloong.lan> (raw)
In-Reply-To: <878us3o8sg.fsf@yeeloong.lan> (Mark H. Weaver's message of "Fri, 21 Mar 2014 11:45:03 -0400")
Mark H Weaver <mhw@netris.org> writes:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Andreas Enge <andreas@enge.fr> skribis:
>>
>>>> Another idea: does your machine have /dev/kvm?
>>>
>>> No.
>>
>> That’s indeed the problem:
>>
>>> 20584 stat("/dev/kvm", 0x7fff2745d348) = -1 ENOENT (No such file or directory)
>>> 20584 futex(0x7f01cf335404, FUTEX_WAKE_PRIVATE, 2147483647) = 0
>>> 20584 write(2, "build error: getting attributes "..., 78) = 78
>>> 20584 exit_group(189) = ?
>>
>> For now, the “solution” is to create it like this:
>>
>> sudo mknod /dev/kvm c 10 232
>
> This is very troubling to me. KVM is not supported on my primary
> platform (Loongson).
Nevermind. I see now that there's no actual dependency on KVM, and that
it merely wants a /dev/kvm node to propagate into the build environment.
Mark
prev parent reply other threads:[~2014-03-21 16:00 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
2014-03-21 15:45 ` Mark H Weaver
2014-03-21 15:59 ` Mark H Weaver [this message]
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=87y503mtkk.fsf@yeeloong.lan \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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.