unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Andreas Enge <andreas@enge.fr>
Cc: Nathan Dehnel <ncdehnel@gmail.com>, help-guix@gnu.org
Subject: Re: What to do if headers are not found
Date: Mon, 4 Jul 2022 16:07:20 +0300	[thread overview]
Message-ID: <YsLmCDZlIwjPNtqG@3900XT> (raw)
In-Reply-To: <YsIBbTcH1uq6qrn+@jurong>

[-- Attachment #1: Type: text/plain, Size: 873 bytes --]

On Sun, Jul 03, 2022 at 10:51:57PM +0200, Andreas Enge wrote:
> 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.
> 

The new syntax would be

(inputs
 (list (list util-linux "lib")))

or

(inputs
 (list `(,util-linux "lib")))

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-07-04 13:39 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
2022-07-03 23:58   ` Nathan Dehnel
2022-07-04 13:07   ` Efraim Flashner [this message]
  -- 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=YsLmCDZlIwjPNtqG@3900XT \
    --to=efraim@flashner.co.il \
    --cc=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).