public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/29834] libpthread.so lacks GLIBC_PRIVATE version for glibc 2.34 and later
Date: Tue, 29 Nov 2022 20:12:46 +0000 [thread overview]
Message-ID: <bug-29834-131-XcHh4olgT3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29834-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29834
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fweimer at redhat dot com
--- Comment #2 from Florian Weimer <fweimer at redhat dot com> ---
Thanks for filing this bug publicly.
Do I understand this correctly? The program does not actually need a definition
of the weak symbol? And we just run into a limitation in the GNU symbol
versioning scheme, where we do not have weak symbol versions at all
(VER_FLG_WEAK is generally understood to mean something else)?
Would it be sufficient if we make this work again by setting an environment
variable?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-29 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 11:53 [Bug nptl/29834] New: " misch at google dot com
2022-11-29 12:11 ` [Bug nptl/29834] " misch at google dot com
2022-11-29 20:12 ` fweimer at redhat dot com [this message]
2022-11-30 12:13 ` misch at google dot com
2022-12-23 9:55 ` misch at google dot com
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=bug-29834-131-XcHh4olgT3@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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).