From: Bartosz Duszel <bartosz.duszel@icloud.com>
To: kei@openmailbox.org
Cc: 23056@debbugs.gnu.org
Subject: bug#23056: (no subject)
Date: Wed, 23 Mar 2016 05:36:58 +0100 [thread overview]
Message-ID: <B8A8D5D8-D343-433F-B5F3-C38BF9F1DF5A@icloud.com> (raw)
In-Reply-To: <87twjyxhtl.fsf@gnu.org>
Hello all,
Had the same issue. Mounting as tmpfs helped. @Kei - thanks for sharing.
Best regards,
dptd
> On 22 Mar 2016, at 23:34, Ludovic Courtès <ludo@gnu.org> wrote:
>
> kei@openmailbox.org skribis:
>
>> On 2016-03-21 18:50, ludo@gnu.org wrote:
>>> Kei <kei@openmailbox.org> skribis:
>>>
>>>> I've managed to get guix to build by running
>>>>
>>>> mount -t tmpfs tmp /tmp
>>>>
>>>> prior to building. I've tried it on two separate hard drives.
>>>
>>> OK, good.
>>>
>>>> Perhaps you can try and replicate my results?
>>>
>>> No, I’d really need to know the answer to the questions at
>>> <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23056#8> to understand.
>>> :-)
>>>
>>> Ludo’.
>>
>> guix-daemon reported itself as version 0.9.0
>> Prior to my mounting /tmp as tmpfs, /tmp was just a folder under /.
>> These details can be seen by using the GuixSD x86_64 USB install image.
>
> Oooh, I see. I hadn’t realized this happened while running the 0.9.0
> installation image.
>
> So what happens is that (1) substitutes were not available for the
> ‘guix’ package, which is why it ended up being built, and (2) /tmp is
> indeed a FUSE file system on the installation image (unionfs), hence the
> weird FUSE things that get in the way when running the tests.
>
> I’ll see what can be done.
>
> Thanks!
>
> Ludo’.
>
>
>
next prev parent reply other threads:[~2016-03-23 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 17:39 bug#23056: Guix 0.9.0 Build Failure Michael Downey
2016-03-18 21:33 ` Ludovic Courtès
2016-03-21 13:45 ` bug#23056: (no subject) Kei
2016-03-21 22:50 ` Ludovic Courtès
2016-03-22 20:43 ` kei
2016-03-22 22:34 ` Ludovic Courtès
2016-03-23 4:36 ` Bartosz Duszel [this message]
2016-03-24 21:48 ` 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=B8A8D5D8-D343-433F-B5F3-C38BF9F1DF5A@icloud.com \
--to=bartosz.duszel@icloud.com \
--cc=23056@debbugs.gnu.org \
--cc=kei@openmailbox.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.