From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/6] gnutls: bump to version 3.2.0
Date: Wed, 15 May 2013 00:36:23 +0200 [thread overview]
Message-ID: <5192BC67.2070600@mind.be> (raw)
In-Reply-To: <1368463259-18958-6-git-send-email-gustavo@zacarias.com.ar>
On 13/05/13 18:40, Gustavo Zacarias wrote:
> Signed-off-by: Gustavo Zacarias<gustavo@zacarias.com.ar>
> ---
> package/gnutls/Config.in | 15 ++++++
> ...gnutls-correct_rpl_gettimeofday_signature.patch | 58 ----------------------
> package/gnutls/gnutls.mk | 29 ++++++++---
> 3 files changed, 38 insertions(+), 64 deletions(-)
> delete mode 100644 package/gnutls/gnutls-correct_rpl_gettimeofday_signature.patch
>
> diff --git a/package/gnutls/Config.in b/package/gnutls/Config.in
> index 038b3fb..6c741a6 100644
> --- a/package/gnutls/Config.in
> +++ b/package/gnutls/Config.in
> @@ -1,6 +1,7 @@
> config BR2_PACKAGE_GNUTLS
> bool "gnutls"
> select BR2_PACKAGE_NETTLE
> + select BR2_PACKAGE_PCRE
> depends on BR2_USE_WCHAR
> help
> GnuTLS is a secure communications library implementing the SSL
> @@ -8,6 +9,20 @@ config BR2_PACKAGE_GNUTLS
>
> http://www.gnutls.org
>
> +config BR2_PACKAGE_GNUTLS_PKCS11
> + bool "PKCS#11 support"
> + depends on !BR2_PREFER_STATIC_LIB
> + depends on BR2_USE_MMU
> + depends on BR2_PACKAGE_GNUTLS
> + depends on BR2_TOOLCHAIN_HAS_THREADS
> + select BR2_PACKAGE_LIBTASN1
> + select BR2_PACKAGE_P11_KIT
> + help
> + Enable PKCS#11 support in gnutls.
> +
> +comment "gnutls pkcs#11 support requires a toolchain with thread support"
> + depends on BR2_PACKAGE_GNUTLS && !BR2_TOOLCHAIN_HAS_THREADS
> +
Any reason why you want to add this config symbol, instead of just
checking for BR2_PACKAGE_P11_KIT in the .mk file?
Regards,
Arnout
--
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:[~2013-05-14 22:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 16:40 [Buildroot] [PATCH 1/6] package infra: remove CPPFLAGS from CFLAGS Gustavo Zacarias
2013-05-13 16:40 ` [Buildroot] [PATCH 2/6] libnspr: bump to version 4.9.6 Gustavo Zacarias
2013-05-13 16:40 ` [Buildroot] [PATCH 3/6] libnss: bump to version 3.14.3 Gustavo Zacarias
2013-05-26 20:14 ` Peter Korsgaard
2013-05-13 16:40 ` [Buildroot] [PATCH 4/6] libcurl: bump to version 7.30.0 Gustavo Zacarias
2013-05-14 22:32 ` Arnout Vandecappelle
2013-05-14 22:47 ` Gustavo Zacarias
2013-05-13 16:40 ` [Buildroot] [PATCH 5/6] p11-kit: new package Gustavo Zacarias
2013-05-13 16:40 ` [Buildroot] [PATCH 6/6] gnutls: bump to version 3.2.0 Gustavo Zacarias
2013-05-14 22:36 ` Arnout Vandecappelle [this message]
2013-05-14 22:49 ` Gustavo Zacarias
2013-05-16 6:17 ` [Buildroot] Config options for optional dependencies [was: [PATCH 6/6] gnutls: bump to version 3.2.0] Arnout Vandecappelle
2013-05-16 8:50 ` Thomas Petazzoni
2013-05-13 17:10 ` [Buildroot] [PATCH 1/6] package infra: remove CPPFLAGS from CFLAGS Thomas Petazzoni
2013-05-13 17:22 ` Gustavo Zacarias
2013-05-13 18:20 ` Thomas Petazzoni
2013-05-13 22:09 ` Gustavo Zacarias
2013-05-13 23:02 ` Arnout Vandecappelle
2013-05-14 7:17 ` Thomas Petazzoni
2013-05-14 8:54 ` Arnout Vandecappelle
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=5192BC67.2070600@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox