From: Ben Hutchings <ben-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>
To: klibc mailing list <klibc-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [ANNOUNCE] klibc 2.0.11
Date: Sun, 02 Oct 2022 01:54:15 +0200 [thread overview]
Message-ID: <a059cb1a79928f64adc3a2401482bb149e604cf4.camel@decadent.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]
I have released version 2.0.11. This is available in the git
repository at:
https://git.kernel.org/pub/scm/libs/klibc/klibc.git
and as a tarball at:
https://mirrors.kernel.org/pub/linux/libs/klibc/2.0/
New features:
- The insmod command has been reinstated
Bug fixes:
- Fixed build failure for some architectures with Linux 5.19 headers
- Fixed infinite recursion in calloc() when built with Clang 14
- Disabled executable stacks in statically linked executables
- Ensured that all executables have some static data, avoiding ELF
loader bugs affecting executables that have only BSS
- arm64: Fixed overwrite of 4 bytes after errno
- A couple of fixes for out-of-tree builds
A git shortlog of changes since version 2.0.10 follows.
Ben.
Ben Hutchings (9):
[klibc] 2.0.10 released, next version is 2.0.11
[klibc] ia64: Fix out-of-tree build
[klibc] Fix header installation from out-of-tree build
[klibc] Kbuild: Properly disable executable stacks in static builds
[klibc] README.klibc: Add note about headers_install in cross-build
[klibc] README.klibc: Update note about building compat user-space
[klibc] fcntl: Fix build failure for some architectures with Linux 5.19
[klibc] Work around ELF loader bugs when executables have only BSS
[klibc] zalloc: Fix infinite recursion with Clang 14
Greg Thelen (2):
[klibc] Revert " remove local insmod.c copy"
[klibc] arm64: store 4 bytes in arm64 errno
--
Ben Hutchings
Hoare's Law of Large Problems:
Inside every large problem is a small problem struggling to get out.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-10-01 23:54 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=a059cb1a79928f64adc3a2401482bb149e604cf4.camel@decadent.org.uk \
--to=ben-/+tvbiectbitmtq+vha3yw@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=klibc-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).