From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] gnupg: depend on libiconv if appropriate
Date: Tue, 04 Feb 2014 10:59:29 +0100 [thread overview]
Message-ID: <52F0BA01.5020806@mind.be> (raw)
In-Reply-To: <BLU0-SMTP112B1A733C43DA19ABF8DF9D9CE0@phx.gbl>
On 30/12/13 18:57, Bernd Kuhls wrote:
>
> Signed-off-by: Bernd Kuhls <berndkuhls@hotmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Ideally, the explanation that you put in the follow-up message should be
in the commit log, but OK.
Regards,
Arnout
> ---
> package/gnupg/gnupg.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/gnupg/gnupg.mk b/package/gnupg/gnupg.mk
> index 39a37d0..c334ac6 100644
> --- a/package/gnupg/gnupg.mk
> +++ b/package/gnupg/gnupg.mk
> @@ -9,7 +9,7 @@ GNUPG_SOURCE = gnupg-$(GNUPG_VERSION).tar.bz2
> GNUPG_SITE = ftp://ftp.gnupg.org/gcrypt/gnupg
> GNUPG_LICENSE = GPLv3+
> GNUPG_LICENSE_FILES = COPYING
> -GNUPG_DEPENDENCIES = zlib ncurses
> +GNUPG_DEPENDENCIES = zlib ncurses $(if $(BR2_PACKAGE_LIBICONV),libiconv)
> GNUPG_CONF_ENV = ac_cv_sys_symbol_underscore=no
> GNUPG_CONF_OPT = --disable-rpath --enable-minimal --disable-regex
>
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-02-04 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 17:57 [Buildroot] [PATCH 1/3] gnupg: depend on libiconv if appropriate Bernd Kuhls
2014-02-02 16:51 ` Bernd Kuhls
2014-02-04 9:59 ` Arnout Vandecappelle [this message]
2014-02-04 10:11 ` Arnout Vandecappelle
2014-02-04 10:25 ` Peter Korsgaard
2014-02-04 10:24 ` Peter Korsgaard
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=52F0BA01.5020806@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.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 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.