From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: Managing data files in workflows
Date: Fri, 26 Mar 2021 13:54:12 +0100 [thread overview]
Message-ID: <m1eeg2hy8b.fsf@ordinateur-de-catherine--konrad.home> (raw)
In-Reply-To: <m1k0puhzbg.fsf@ordinateur-de-catherine--konrad.home>
Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
> Maybe it's time to switch to the development version of GWL!
Not as obvious as I thought: it doesn't build.
$ guix build -L channel -f .guix.scm
starts out saying
The following derivations will be built:
/gnu/store/b62d2v6210p8j27fcx7z08xb3lcjw5hi-gwl-0.3.0.drv
/gnu/store/prx66i4jvs445g82gkc5sv7p7hhf27ba-guile-lib-0.2.7.drv
building /gnu/store/prx66i4jvs445g82gkc5sv7p7hhf27ba-guile-lib-0.2.7.drv...
and many lines later fails with
/tmp/guix-build-guile-lib-0.2.7.drv-0/guile-lib-0.2.7/build-aux/missing: line 81: makeinfo: command not found
WARNING: 'makeinfo' is missing on your system.
Note that
$ guix build --check guile-lib
works just fine, so the failure must somehow involve the additional
channel. Unfortunately I don't understand the guile-replacing magic in
there well enough for any serious debugging.
Cheers,
Konrad.
next prev parent reply other threads:[~2021-03-26 12:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 9:57 Managing data files in workflows Konrad Hinsen
2021-03-26 7:02 ` zimoun
2021-03-26 12:46 ` Konrad Hinsen
2021-03-26 8:47 ` Ricardo Wurmus
2021-03-26 12:30 ` Konrad Hinsen
2021-03-26 12:54 ` Konrad Hinsen [this message]
2021-03-26 13:13 ` Ricardo Wurmus
2021-03-26 15:36 ` Konrad Hinsen
2021-04-01 13:27 ` Ricardo Wurmus
2021-04-02 8:41 ` Konrad Hinsen
2021-04-07 11:38 ` Ricardo Wurmus
2021-04-08 7:28 ` Konrad Hinsen
2021-05-03 9:18 ` Ricardo Wurmus
2021-05-03 11:58 ` zimoun
2021-05-03 13:47 ` Ricardo Wurmus
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://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1eeg2hy8b.fsf@ordinateur-de-catherine--konrad.home \
--to=konrad.hinsen@fastmail.net \
--cc=gwl-devel@gnu.org \
--cc=rekado@elephly.net \
/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).