From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: bug-guix@gnu.org
Subject: Re: Assertion failure while building libtool
Date: Sat, 15 Jun 2013 15:20:17 +0200 [thread overview]
Message-ID: <87r4g38q9a.fsf@gnu.org> (raw)
In-Reply-To: <8761xou0up.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 08 Jun 2013 16:35:26 +0200")
ludo@gnu.org (Ludovic Courtès) skribis:
> Hi Mark,
>
> Mark H Weaver <mhw@netris.org> skribis:
>
>> ludo@gnu.org (Ludovic Courtès) writes:
>>
>>> Mark H Weaver <mhw@netris.org> skribis:
>>>
>>>> I did a clean rebuild of guix from git master (make clean; ./bootstrap;
>>>> make), and then attempted to upgrade all packages. After several
>>>> successful builds, the daemon printed this:
>>>>
>>>> guix-daemon: nix/libstore/local-store.cc:526: void
>>>> nix::canonicalisePathMetaData_(const Path&, uid_t,
>>>> nix::InodesSeen&): Assertion `!((((st.st_mode)) & 0170000) ==
>>>> (0040000))' failed.
>>>
>>> Yes, this is a daemon bug pending a fix:
>>> <https://github.com/NixOS/nix/issues/122>.
>>>
>>> In the meantime, you can hopefully work around it by deleting the
>>> already-present output–i.e., by running either:
>>>
>>> guix gc --delete /nix/store/wbsypglflcy7fi08h4finffjy9mqzh12-libtool-2.4.2
>>
>> This command fails because there are still references:
>
> OK. I believe this (untested) patch fixes the underlying problem:
Commit 16357e8 updates the ‘nix-upstream’ submodule to the latest Nix,
which has a fix for this problem. Re-run ./bootstrap to get it.
Details at https://github.com/NixOS/nix/issues/122 .
Ludo’.
prev parent reply other threads:[~2013-06-15 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 17:25 Assertion failure while building libtool Mark H Weaver
2013-06-07 20:49 ` Ludovic Courtès
2013-06-08 2:45 ` Mark H Weaver
2013-06-08 14:35 ` Ludovic Courtès
2013-06-08 18:04 ` Mark H Weaver
2013-06-08 22:57 ` Ludovic Courtès
2013-06-15 13:20 ` Ludovic Courtès [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=87r4g38q9a.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=mhw@netris.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.