From: Florian Weimer via Libc-alpha <firstname.lastname@example.org> To: email@example.com Subject: [PATCH] NEWS: Mention libpthread, libdl, libutil, libanl integration Date: Wed, 21 Jul 2021 14:08:49 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) --- NEWS | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/NEWS b/NEWS index efc105b6b4..dd333109a5 100644 --- a/NEWS +++ b/NEWS @@ -9,6 +9,20 @@ Version 2.34 Major new features: +* All functionality formerly implemented in the libraries libpthread, + libdl, libutil, libanl has been integrated into libc. New + applications do not link with -lpthread, -ldl, -lutil, -lanl anymore. + For backwards compatibility, empty static archives libpthread.a, + libdl.a, libutil.a, libanl.a are provided, so that the linker options + keep working. Applications which have been linked against glibc 2.33 + or earlier continue to load the corresponding shared objects (which + are now empty). The integration of those libraries into libc means + that additional symbols become available by default. This can cause + applications that contain weak references to take unexpected code + paths that would only have been used in previous glibc versions when + e.g. preloading libpthread.so.0, potentially exposing application + bugs. + * When _DYNAMIC_STACK_SIZE_SOURCE or _GNU_SOURCE are defined, PTHREAD_STACK_MIN is no longer constant and is redefined to sysconf(_SC_THREAD_STACK_MIN).
next reply other threads:[~2021-07-21 12:09 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-21 12:08 Florian Weimer via Libc-alpha [this message] 2021-07-29 2:19 ` Carlos O'Donell via Libc-alpha 2021-07-29 7:56 ` Alexander Monakov via Libc-alpha 2021-10-08 22:09 ` Stafford Horne via Libc-alpha 2021-10-09 12:18 ` Florian Weimer 2021-10-10 0:45 ` Stafford Horne via Libc-alpha 2021-10-10 13:34 ` Florian Weimer
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 List information: https://www.gnu.org/software/libc/involved.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH] NEWS: Mention libpthread, libdl, libutil, libanl integration' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/glibc.git 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).