From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: Re: [ptxdist] [APPLIED] libgcrypt: version bump 1.8.8 -> 1.10.1
Date: Thu, 4 Aug 2022 17:14:26 +0200 [thread overview]
Message-ID: <20220804151426.175954-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220729092654.3861-3-bruno.thomsen@gmail.com>
Thanks, applied as 40e2a62009ed477983f56c8dcc788e08233e584b.
Michael
[sent from post-receive hook]
On Thu, 04 Aug 2022 17:14:26 +0200, Bruno Thomsen <bruno.thomsen@gmail.com> wrote:
> 5 new configure options:
> --enable-force-soft-hwfeatures
> --disable-shaext-support
> --disable-ppc-crypto-support
> --disable-instrumentation-munging
> --with-fips-module-version=VERSION
>
> Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
> Message-Id: <20220729092654.3861-3-bruno.thomsen@gmail.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libgcrypt.make b/rules/libgcrypt.make
> index 8b0b39d0965a..3da2f434ce5e 100644
> --- a/rules/libgcrypt.make
> +++ b/rules/libgcrypt.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBGCRYPT) += libgcrypt
> #
> # Paths and names
> #
> -LIBGCRYPT_VERSION := 1.8.8
> -LIBGCRYPT_MD5 := 252045343c586e5261134c91330f5b90
> +LIBGCRYPT_VERSION := 1.10.1
> +LIBGCRYPT_MD5 := 8fadbe1fddafa341dce5ef3869f70e25
> LIBGCRYPT := libgcrypt-$(LIBGCRYPT_VERSION)
> LIBGCRYPT_SUFFIX := tar.bz2
> LIBGCRYPT_URL := https://www.gnupg.org/ftp/gcrypt/libgcrypt/$(LIBGCRYPT).$(LIBGCRYPT_SUFFIX)
> @@ -57,10 +57,12 @@ LIBGCRYPT_AUTOCONF := \
> --$(call ptx/endis,LIBGCRYPT_ASM)-asm \
> --disable-m-guard \
> --disable-large-data-tests \
> + --disable-force-soft-hwfeatures \
> --disable-hmac-binary-check \
> --enable-jent-support \
> --enable-padlock-support \
> --enable-aesni-support \
> + --disable-shaext-support \
> --enable-pclmul-support \
> --enable-sse41-support \
> --enable-drng-support \
> @@ -68,7 +70,9 @@ LIBGCRYPT_AUTOCONF := \
> --enable-avx2-support \
> --$(call ptx/endis,PTXCONF_ARCH_ARM_NEON)-neon-support \
> --enable-arm-crypto-support \
> + --disable-ppc-crypto-support \
> --enable-O-flag-munging \
> + --disable-instrumentation-munging \
> --disable-amd64-as-feature-detection \
> --enable-optimization \
> --enable-noexecstack \
next prev parent reply other threads:[~2022-08-04 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 9:26 [ptxdist] [PATCH 1/6] npth: version bump 1.5 -> 1.6 Bruno Thomsen
2022-07-29 9:26 ` [ptxdist] [PATCH 2/6] libgpg-error: version bump 1.42 -> 1.45 Bruno Thomsen
2022-08-04 15:14 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-29 9:26 ` [ptxdist] [PATCH 3/6] libgcrypt: version bump 1.8.8 -> 1.10.1 Bruno Thomsen
2022-08-04 15:14 ` Michael Olbrich [this message]
2022-07-29 9:26 ` [ptxdist] [PATCH 4/6] libksba: version bump 1.3.5 -> 1.6.0 Bruno Thomsen
2022-08-04 15:14 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-29 9:26 ` [ptxdist] [PATCH 5/6] gnupg: version bump 2.2.23 -> 2.3.7 Bruno Thomsen
2022-08-05 7:50 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-29 9:26 ` [ptxdist] [PATCH 6/6] gnupg: add license files and update spdx identifiers Bruno Thomsen
2022-07-29 10:38 ` Michael Olbrich
2022-08-04 15:14 ` [ptxdist] [APPLIED] npth: version bump 1.5 -> 1.6 Michael Olbrich
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=20220804151426.175954-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=bruno.thomsen@gmail.com \
--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