From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] libxcrypt: Update to 4.4.19
Date: Wed, 14 Apr 2021 13:57:19 +0200 [thread overview]
Message-ID: <20210414115719.3669391-1-adolf.belka@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1780 bytes --]
- Update from 4.4.17 to 4.4.19
- Update of rootfile not needed
- Changelog
libxcrypt NEWS -- history of user-visible changes.
Version 4.4.19
* Improve fallback implementation of explicit_bzero.
* Add glibc-on-CSKY, ARC, and RISCV-32 entries to libcrypt.minver.
These were added in GNU libc 2.29, 2.32, and 2.33 respectively
(issue #122).
* Do not build xcrypt.h if we’re not going to install it.
* Do not apply --enable-obsolete-api-enosys mode to fcrypt.
* Compilation fix for NetBSD. NetBSD’s <unistd.h> declares encrypt
and setkey to return int, contrary to POSIX (which says they return
void). Rename those declarations out of the way with macros.
* Compilation fixes for building with GCC 11.
Basically fixes for explicit type-casting.
* Force update of existing symlinks during installation (issue #120).
Version 4.4.18
* Fix compilation errors on (Free)BSD (issue #110).
* Fix conversion error in lib/alg-gost3411-core.c, which is seen by
some sensitive compilers.
* Convert build scripts to Perl.
The minimum version of Perl required is 5.14.
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
lfs/libxcrypt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lfs/libxcrypt b/lfs/libxcrypt
index 8fb937c9b..c452034c9 100644
--- a/lfs/libxcrypt
+++ b/lfs/libxcrypt
@@ -24,7 +24,7 @@
include Config
-VER = 4.4.17
+VER = 4.4.19
THISAPP = libxcrypt-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -45,7 +45,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 12118d098ead971f9a8377cacfdd0da7
+$(DL_FILE)_MD5 = a088bd62745b1e29a9318eb5a44c09f7
install : $(TARGET)
--
2.31.1
reply other threads:[~2021-04-14 11:57 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=20210414115719.3669391-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