all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Paul van der Walt <paul@denknerd.org>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: ncmpcpp: Enable taglib support.
Date: Sun, 08 Mar 2015 22:30:01 +0100	[thread overview]
Message-ID: <87385fqism.fsf@gnu.org> (raw)
In-Reply-To: <E1YUEXM-0005oq-0e@vcs.savannah.gnu.org> (paul@denknerd.org's message of "Sat, 07 Mar 2015 13:13:00 +0000")

Howdy!

Paul <paul@denknerd.org> skribis:

> commit cd77777602af48a32466d8d720a6c70a89721607
> Author: Paul van der Walt <paul@denknerd.org>
> Date:   Sat Mar 7 13:40:40 2015 +0100
>
>     gnu: ncmpcpp: Enable taglib support.
>     
>     * gnu/packages/mpd.scm (ncmpcpp): Add --with-taglib configure flag.

[...]

> diff --git a/gnu/packages/mpd.scm b/gnu/packages/mpd.scm
> index 2313b30..2f9ad72 100644
> --- a/gnu/packages/mpd.scm
> +++ b/gnu/packages/mpd.scm
> @@ -196,10 +196,11 @@ terminal using ncurses.")
>       `(("pkg-config" ,pkg-config)
>         ("automake" ,automake)
>         ("autoconf" ,autoconf)
> -       ("libtool" ,libtool)))
> +       ("libtool" ,libtool)
> +       ("taglib" ,taglib)))

‘taglib’ should go to a new ‘inputs’ field, not to ‘native-inputs’ (the
distinction between the two is for when cross-compiling: ‘native-inputs’
are things that need to be run on the machine that compiles, whereas
‘inputs’ is code to run on the target machine.)

Could you adjust accordingly?

Thanks,
Ludo’.

       reply	other threads:[~2015-03-08 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150307131259.22314.37235@vcs.savannah.gnu.org>
     [not found] ` <E1YUEXM-0005oq-0e@vcs.savannah.gnu.org>
2015-03-08 21:30   ` Ludovic Courtès [this message]
2015-03-09  9:57     ` 01/01: gnu: ncmpcpp: Enable taglib support Paul van der Walt
2015-03-09 19:45       ` Ludovic Courtès
2015-03-09 10:03     ` [PATCH] gnu: ncmpcpp: Move taglib from native-inputs Paul van der Walt

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87385fqism.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=paul@denknerd.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.