public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "misch at google dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nptl/29834] New: libpthread.so lacks GLIBC_PRIVATE version for glibc 2.34 and later Date: Tue, 29 Nov 2022 11:53:19 +0000 [thread overview] Message-ID: <bug-29834-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29834 Bug ID: 29834 Summary: libpthread.so lacks GLIBC_PRIVATE version for glibc 2.34 and later Product: glibc Version: 2.34 Status: UNCONFIRMED Severity: normal Priority: P2 Component: nptl Assignee: unassigned at sourceware dot org Reporter: misch at google dot com CC: drepper.fsp at gmail dot com Target Milestone: --- Created attachment 14474 --> https://sourceware.org/bugzilla/attachment.cgi?id=14474&action=edit Patch to restore GLIBC_PRIVATE version for libpthread.so Since glibc 2.34 libpthread.so no longer provides the GLIBC_PRIVATE version. This in turn causes problems with closed source software which we can't recompile ourselves. I've filed this bug to discuss if it would make sense to restore the GLIBC_PRIVATE version. Details: Commit e8d52b64a54ba9ed7778ca9ce1f084eb5808f8d1 [1] removed the GLIBC_PRIVATE version from libthread.so. This in turn caused closed source software by Synopsys [2] to fail with this error: $ /opt/synopsys/vcs/T-2022.06-SP1-1/linux64/bin/vcs1 -h /opt/synopsys/vcs/T-2022.06-SP1-1/linux64/bin/vcs1: /lib/x86_64-linux-gnu/libpthread.so.0: version `GLIBC_PRIVATE' not found (required by /opt/synopsys/vcs/T-2022.06-SP1-1/linux64/bin/vcs1) It turns out that the Synopsys binaries have a weak symbol for __pthread_unwind@GLIBC_PRIVATE. Synopsys support is slow and so for the time being we've helped ourselves by patching glibc to provide the GLIBC_PRIVATE version again for libpthread.so (see attached patch). [1] https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=e8d52b64a54ba9ed7778ca9ce1f084eb5808f8d1 [2] https://www.synopsys.com/ -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-11-29 11:53 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-29 11:53 misch at google dot com [this message] 2022-11-29 12:11 ` [Bug nptl/29834] " misch at google dot com 2022-11-29 20:12 ` fweimer at redhat dot com 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@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: linkBe 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).