From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH v2] libxcrypt: Update to version 4.4.38
Date: Sun, 23 Feb 2025 19:14:19 +0100 [thread overview]
Message-ID: <20250223181419.1224379-1-adolf.belka@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3250 bytes --]
- Update from version 4.4.36 to 4.4.38
- Update of rootfile not required
- in version 4.4.37 pkg-config was made a dependency for building libxcrypt. This caused
user(s) a problem when libxcrypt was being built before pkg-config wasw available.
- In version 4.4.38 it was allowed that if pkg-config was not available then the build
would continue and complete but any installation of .pc files was no longer carried
out.
- moved pkg-config to before libxcrypt so that the libxcrypt.pc file is installed in the
build environment and the libcrypt.pc file linked to it, the same as used to occur in
version 4.4.36
- Changelog
4.4.38
* Fix several "-Wunterminated-string-initialization", which are seen by
upcoming GCC 15.x (issue #194).
* Fix "-Wmaybe-uninitialized" in crypt.c, which is seen by GCC 13.3.0.
* Skip test/explicit-bzero if compiling with ASAN.
* Drop hard requirement for the pkg-config binary (issue #198).
4.4.37
* Several fixes to the manpages (issue #185).
* Add binary compatibility for x86_64 GNU/Hurd (issue #189).
* Only test the needed makecontext signature during configure (issue #178).
* Fix -Werror=strict-overflow in lib/crypt-bcrypt.c, which is seen
by GCC 4.8.5 (issue #197).
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
lfs/libxcrypt | 6 +++---
make.sh | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/lfs/libxcrypt b/lfs/libxcrypt
index 4ec63516a..2f40385ca 100644
--- a/lfs/libxcrypt
+++ b/lfs/libxcrypt
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2023 IPFire Team <info(a)ipfire.org> #
+# Copyright (C) 2007-2025 IPFire Team <info(a)ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -24,7 +24,7 @@
include Config
-VER = 4.4.36
+VER = 4.4.38
THISAPP = libxcrypt-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -47,7 +47,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 9f028e0fe2cb7bb4273f3f6d1e579e0fe93cd71eba21286aa7dc078c904ea3cdce38b2955bdcd618853f7657b01aea7e28c4d898680e69fdf75f812b5a304c1d
+$(DL_FILE)_BLAKE2 = 42d594fe36f61a1b5343d9fda22541b09373fe74c587537db8203f9c92120b6c73edef2e1b3d7febda14ae979845405b5fdaeb31dd2b89eedc423b0924ea7cff
install : $(TARGET)
diff --git a/make.sh b/make.sh
index 2910ff7a4..6258705fe 100755
--- a/make.sh
+++ b/make.sh
@@ -1420,6 +1420,7 @@ build_system() {
lfsmake2 gmp
lfsmake2 mpfr
lfsmake2 libmpc
+ lfsmake2 pkg-config
lfsmake2 libxcrypt
lfsmake2 file
lfsmake2 gcc
@@ -1455,7 +1456,6 @@ build_system() {
lfsmake2 whois
lfsmake2 kbd
lfsmake2 less
- lfsmake2 pkg-config
lfsmake2 procps
lfsmake2 make
lfsmake2 libpipeline
--
2.48.1
reply other threads:[~2025-02-23 18:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250223181419.1224379-1-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/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