From: Bastian Krause <bst@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bastian Krause <bst@pengutronix.de>
Subject: [ptxdist] [PATCH 1/5] cryptsetup: version bump 2.0.3 -> 2.0.6
Date: Fri, 8 Feb 2019 10:12:15 +0100 [thread overview]
Message-ID: <20190208091219.1603-1-bst@pengutronix.de> (raw)
cryptsetup strongly encourages to link against libblkid since 2.0.4.
There's no point in enabling an SSE implementation on embedded devices.
Signed-off-by: Bastian Krause <bst@pengutronix.de>
---
rules/cryptsetup.in | 1 +
rules/cryptsetup.make | 6 ++++--
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/rules/cryptsetup.in b/rules/cryptsetup.in
index 67ce41beb..1a4f8f814 100644
--- a/rules/cryptsetup.in
+++ b/rules/cryptsetup.in
@@ -5,6 +5,7 @@ menuconfig CRYPTSETUP
select LVM2
select LIBUUID
select LIBPOPT
+ select LIBBLKID
select LIBGCRYPT if CRYPTSETUP_CRYPT_BACKEND_GCRYPT
select OPENSSL if CRYPTSETUP_CRYPT_BACKEND_OPENSSL
select NETTLE if CRYPTSETUP_CRYPT_BACKEND_NETTLE
diff --git a/rules/cryptsetup.make b/rules/cryptsetup.make
index fbc30d868..ec82b4add 100644
--- a/rules/cryptsetup.make
+++ b/rules/cryptsetup.make
@@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_CRYPTSETUP) += cryptsetup
#
# Paths and names
#
-CRYPTSETUP_VERSION := 2.0.3
-CRYPTSETUP_MD5 := 9161132f69e97018b39ab592d7831f61
+CRYPTSETUP_VERSION := 2.0.6
+CRYPTSETUP_MD5 := c01aa63a90acdb25600ed9126fa2b1a1
CRYPTSETUP := cryptsetup-$(CRYPTSETUP_VERSION)
CRYPTSETUP_SUFFIX := tar.gz
CRYPTSETUP_URL := https://www.kernel.org/pub/linux/utils/cryptsetup/v$(basename $(CRYPTSETUP_VERSION))/$(CRYPTSETUP).$(CRYPTSETUP_SUFFIX)
@@ -52,6 +52,8 @@ CRYPTSETUP_CONF_OPT := \
--$(call ptx/endis, PTXCONF_CRYPTSETUP_CRYPT_BACKEND_GCRYPT)-gcrypt-pbkdf2 \
--enable-internal-argon2 \
--disable-libargon2 \
+ --disable-internal-sse-argon2 \
+ --enable-blkid \
--enable-dev-random \
--disable-python \
--with-crypto_backend=$(PTXCONF_CRYPTSETUP_CRYPT_BACKEND) \
--
2.20.1
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2019-02-08 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 9:12 Bastian Krause [this message]
2019-02-08 9:12 ` [ptxdist] [PATCH 2/5] host-json-c: new package Bastian Krause
2019-02-08 9:12 ` [ptxdist] [PATCH 3/5] host-libpopt: " Bastian Krause
2019-02-08 9:12 ` [ptxdist] [PATCH 4/5] host-lvm2: " Bastian Krause
2019-02-08 9:12 ` [ptxdist] [PATCH 5/5] host-cryptsetup: " Bastian Krause
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=20190208091219.1603-1-bst@pengutronix.de \
--to=bst@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