From: ludo@gnu.org (Ludovic Courtès)
To: Dave Love <fx@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: fixing --check saying outputs not valid
Date: Fri, 08 Sep 2017 22:56:23 +0200 [thread overview]
Message-ID: <87wp589afc.fsf@gnu.org> (raw)
In-Reply-To: <87bmmlpm8m.fsf@albion.it.manchester.ac.uk> (Dave Love's message of "Fri, 08 Sep 2017 10:34:33 +0100")
Dave Love <fx@gnu.org> skribis:
> I ran build --check on a new package and it complained that some output
> of the derivation aren't valid. Then I checked hwloc, which also has a
> "lib" output and it has the same problem:
>
> guix build: error: build failed: some outputs of `/gnu/store/bsafscmmaw43ssb0lhnri3vdi0wi0chx-hwloc-1.11.7.drv' are not valid, so checking is not possible
>
> With --verbosity=4, it looks as if that's due to
>
> | | path `/gnu/store/fsch2h9r8jp3c5ahs0b0mr8pr4yp4l3q-hwloc-1.11.7-lib' is required, but there is no substituter that can build it
>
> How could I fix that?
To run --check, you must first already have the store item(s) available.
So you would first run:
guix build hwloc
which will ensure both hwloc and hwloc:lib are in your store, possibly
by downloading substitutes.
Then you can run “guix build hwloc --check -L --no-grafts”, which will
build hwloc locally and raise an error if hwloc:{out,lib} are not
bit-identical to what you had in store.
Makes sense?
(The “--no-grafts” part is because what you care about is the actual
build of hwloc, not the grafting derivation.)
Ludo’.
next prev parent reply other threads:[~2017-09-08 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 9:34 fixing --check saying outputs not valid Dave Love
2017-09-08 20:56 ` Ludovic Courtès [this message]
2017-09-11 10:31 ` Dave Love
2017-09-11 12:14 ` Ludovic Courtès
2017-09-13 13:27 ` Dave Love
2017-09-14 8:18 ` 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=87wp589afc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=fx@gnu.org \
--cc=help-guix@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.
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).