mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 1/3] libgcrypt: version bump to 1.8 stable release
Date: Mon, 28 Aug 2017 12:17:48 +0200	[thread overview]
Message-ID: <20170828101750.19361-1-jbe@pengutronix.de> (raw)

From the announcement:
"This is a new stable version of Libgcrypt with full API
and ABI compatibility to the 1.7 series.  Its main features are support
Blake-2, XTS mode, an improved RNG, and performance improvements for the
ARM architecture."

Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
---
 rules/libgcrypt.make | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/rules/libgcrypt.make b/rules/libgcrypt.make
index 3fff3f379..43c8f3a7e 100644
--- a/rules/libgcrypt.make
+++ b/rules/libgcrypt.make
@@ -17,8 +17,8 @@ PACKAGES-$(PTXCONF_LIBGCRYPT) += libgcrypt
 #
 # Paths and names
 #
-LIBGCRYPT_VERSION	:= 1.7.8
-LIBGCRYPT_MD5		:= 34fd2e6d230cbe56799cdf7df05f56c5
+LIBGCRYPT_VERSION	:= 1.8.0
+LIBGCRYPT_MD5		:= 530db74602b558209f9ad7356a680971
 LIBGCRYPT		:= libgcrypt-$(LIBGCRYPT_VERSION)
 LIBGCRYPT_SUFFIX	:= tar.bz2
 LIBGCRYPT_URL		:= http://artfiles.org/gnupg.org/libgcrypt/$(LIBGCRYPT).$(LIBGCRYPT_SUFFIX) ftp://ftp.gnupg.org/gcrypt/libgcrypt/$(LIBGCRYPT).$(LIBGCRYPT_SUFFIX)
@@ -59,6 +59,7 @@ LIBGCRYPT_AUTOCONF := \
 	--disable-m-guard \
 	--disable-large-data-tests \
 	--disable-hmac-binary-check \
+	--enable-jent-support \
 	--enable-padlock-support \
 	--enable-aesni-support \
 	--enable-pclmul-support \
-- 
2.11.0


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2017-08-28 10:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28 10:17 Juergen Borleis [this message]
2017-08-28 10:17 ` [ptxdist] [PATCH 2/3] which: version bump and large file awareness Juergen Borleis
2017-08-28 10:17 ` [ptxdist] [PATCH 3/3] libseccomp: install some useful development tools on demand Juergen Borleis

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=20170828101750.19361-1-jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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