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 08:59:52 +0200 [thread overview]
Message-ID: <YsE+aN5If0pI76pQ@jurong> (raw)
In-Reply-To: <CAEEhgEvB4p4s34qfbJ8odz11puAk57Ht1X5J_qRn_oV_vhJsDg@mail.gmail.com>
Am Sat, Jul 02, 2022 at 06:44:20PM -0500 schrieb Nathan Dehnel:
> This is a package I'm making. Configure can't find libmount.h, which
> comes from util-linux, even though I have added it to
> propagated-inputs, as the manual suggests. How can I fix this or
> further investigate?
Very quick answer: Try to add it to normal inputs.
Propagated inputs are packages that are installed when the new package is
installed; this covers cases when the new package cannot *run* without the
propagated input, broadly speaking. They may not even be around when
building the new package (I do not remember how this works, but your
experience seems to indicate it).
Andreas
next prev parent reply other threads:[~2022-07-03 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 23:44 What to do if headers are not found Nathan Dehnel
2022-07-03 6:59 ` Andreas Enge [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-03 20:40 Nathan Dehnel
2022-07-03 20:51 ` Andreas Enge
2022-07-03 23:58 ` Nathan Dehnel
2022-07-04 13:07 ` Efraim Flashner
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=YsE+aN5If0pI76pQ@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).