From: Andreas Enge <andreas@enge.fr>
To: Nathan Dehnel <ncdehnel@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: What to do if headers are not found
Date: Sun, 3 Jul 2022 22:51:57 +0200 [thread overview]
Message-ID: <YsIBbTcH1uq6qrn+@jurong> (raw)
In-Reply-To: <CAEEhgEvP0uXq5CJzoyecDvER9d-NqZ2mYVCXQqKJxCY2Sa9New@mail.gmail.com>
Am Sun, Jul 03, 2022 at 03:40:22PM -0500 schrieb Nathan Dehnel:
> That didn't work, unfortunately.
If you try "guix build util-linux", you will see that there are three
outputs. The header files are in the lib output, so you need to add
(inputs
`(("util-linux" ,util-linux "lib")))
(And maybe something different with the new syntax, but it works this way.)
Then it passes this hurdle, and complains about a missing dbus package next.
Andreas
next prev parent reply other threads:[~2022-07-03 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 20:40 What to do if headers are not found Nathan Dehnel
2022-07-03 20:51 ` Andreas Enge [this message]
2022-07-03 23:58 ` Nathan Dehnel
2022-07-04 13:07 ` Efraim Flashner
-- strict thread matches above, loose matches on Subject: below --
2022-07-02 23:44 Nathan Dehnel
2022-07-03 6:59 ` Andreas Enge
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=YsIBbTcH1uq6qrn+@jurong \
--to=andreas@enge.fr \
--cc=help-guix@gnu.org \
--cc=ncdehnel@gmail.com \
/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).