From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libxcrypt: Version bump. 4.4.38 -> 4.5.1
Date: Thu, 4 Dec 2025 14:14:38 +0100 [thread overview]
Message-ID: <20251204131438.2195977-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20251108194204.2396283-1-christian.melki@t2data.com>
Thanks, applied as fab44dc01f1579cabf68e1be6a1b39f3c6ff5ac9.
Michael
[sent from post-receive hook]
On Thu, 04 Dec 2025 14:14:38 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> https://github.com/besser82/libxcrypt/releases/tag/v4.5.0
> https://github.com/besser82/libxcrypt/releases/tag/v4.5.1
>
> * Sort and extend config options according to configure_helper.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20251108194204.2396283-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libxcrypt.make b/rules/libxcrypt.make
> index a516926f3458..2c03057ff0da 100644
> --- a/rules/libxcrypt.make
> +++ b/rules/libxcrypt.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBXCRYPT) += libxcrypt
> #
> # Paths and names
> #
> -LIBXCRYPT_VERSION := 4.4.38
> -LIBXCRYPT_MD5 := 1796a5d20098e9dd9e3f576803c83000
> +LIBXCRYPT_VERSION := 4.5.1
> +LIBXCRYPT_MD5 := 7be4cacda2055aa41133f7a577512a08
> LIBXCRYPT := libxcrypt-$(LIBXCRYPT_VERSION)
> LIBXCRYPT_SUFFIX := tar.xz
> LIBXCRYPT_URL := https://github.com/besser82/libxcrypt/releases/download/v$(LIBXCRYPT_VERSION)/$(LIBXCRYPT).$(LIBXCRYPT_SUFFIX)
> @@ -41,13 +41,21 @@ HASH_METHODS := glibc,strong
> LIBXCRYPT_CONF_TOOL := autoconf
> LIBXCRYPT_CONF_OPT := \
> $(CROSS_AUTOCONF_USR) \
> - --disable-failure-tokens \
> + $(GLOBAL_LARGE_FILE_OPTION) \
> + --disable-werror \
> --disable-static \
> + --disable-symvers \
> --disable-valgrind \
> + --disable-valgrind-memcheck \
> + --enable-valgrind-helgrind \
> + --disable-valgrind-drd \
> + --disable-valgrind-sgcheck \
> + --disable-failure-tokens \
> + --enable-xcrypt-compat-files \
> --enable-obsolete-api \
> --enable-obsolete-api-enosys=$(call ptx/ifdef,PTXCONF_LIBXCRYPT_OBSOLETE_STUBS,yes,no) \
> --enable-hashes=$(HASH_METHODS) \
> - --enable-xcrypt-compat-files
> + --$(call ptx/endis, PTXDIST_Y2038)-year2038
>
> # ----------------------------------------------------------------------------
> # Target-Install
prev parent reply other threads:[~2025-12-04 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-08 19:42 [ptxdist] [PATCH] " Christian Melki
2025-12-04 13:14 ` Michael Olbrich [this message]
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=20251204131438.2195977-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.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