From: Michael Hudson-Doyle via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org, bug-gnulib@gnu.org, binutils@sourceware.org
Subject: Re: Undefined use of weak symbols in gnulib
Date: Mon, 12 Jul 2021 22:04:11 +1200 [thread overview]
Message-ID: <CAJ8wqtfX2yn721W=hKZTByxBRRPxxGDLOEw8t6+6rfQUb3oGWA@mail.gmail.com> (raw)
In-Reply-To: <87o8e0p92r.fsf@oldenburg.str.redhat.com>
On Tue, 27 Apr 2021 at 17:53, Florian Weimer <fweimer@redhat.com> wrote:
> lib/glthread/lock.h has this:
>
> | /* The way to test at runtime whether libpthread is present is to test
> | whether a function pointer's value, such as &pthread_mutex_init, is
> | non-NULL. However, some versions of GCC have a bug through which, in
> | PIC mode, &foo != NULL always evaluates to true if there is a direct
> | call to foo(...) in the same function. To avoid this, we test the
> | address of a function in libpthread that we don't use. */
>
[snip]
This will become an urgent issue with glibc 2.34, which defines
> pthread_mutexattr_gettype unconditionally. Certain gnulib modules will
> stop working until the binaries are relinked. I expect the issue is
> already visible with earlier glibc versions if libpthread is
> unexpectedly present at run time.
>
Did this thread ever reach a conclusion? I'm testing a snapshot of glibc
2.34 in ubuntu and running into this issue -- bison segfaults on startup on
ppc64el. There is some talk of 'rebuilding the world' once 2.34 lands in a
distro but that might be hard because I suspect the world might be too
broken to do that (maybe it's not that bad really... but it doesn't sound
like fun).
Cheers,
mwh
next prev parent reply other threads:[~2021-07-12 10:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 5:53 Undefined use of weak symbols in gnulib Florian Weimer via Libc-alpha
2021-04-27 6:50 ` Paul Eggert
2021-04-27 6:58 ` Florian Weimer via Libc-alpha
2021-04-27 7:13 ` Paul Eggert
2021-04-27 7:24 ` Andreas Schwab
2021-04-27 11:06 ` Florian Weimer via Libc-alpha
2021-04-28 0:09 ` Bruno Haible
2021-04-28 2:10 ` H.J. Lu via Libc-alpha
2021-04-28 2:13 ` H.J. Lu via Libc-alpha
2021-05-05 20:31 ` Fangrui Song
2021-04-28 8:35 ` Florian Weimer via Libc-alpha
2021-04-28 13:15 ` Michael Matz
2021-04-28 7:44 ` Florian Weimer via Libc-alpha
2021-04-28 14:48 ` Bruno Haible
2021-04-28 17:44 ` Florian Weimer via Libc-alpha
2021-07-17 14:38 ` Bruno Haible
2021-07-17 14:55 ` Florian Weimer via Libc-alpha
2021-07-17 16:39 ` Bruno Haible
2021-07-27 20:02 ` Joseph Myers
2021-07-27 20:19 ` Florian Weimer via Libc-alpha
2021-07-27 23:38 ` Paul Eggert
2021-04-27 23:22 ` Bruno Haible
2021-04-27 23:47 ` Bruno Haible
2021-04-28 7:57 ` Florian Weimer via Libc-alpha
2021-04-28 14:40 ` Bruno Haible
2021-04-28 17:43 ` Florian Weimer via Libc-alpha
2021-04-29 15:15 ` Bruno Haible
2021-04-30 9:55 ` Florian Weimer via Libc-alpha
2021-04-29 6:33 ` Ben Pfaff via Libc-alpha
2021-05-03 1:44 ` Alan Modra via Libc-alpha
2021-07-12 10:04 ` Michael Hudson-Doyle via Libc-alpha [this message]
2021-07-12 15:03 ` Florian Weimer via Libc-alpha
2021-07-12 15:30 ` Matthias Klose
2021-07-12 15:37 ` Florian Weimer via Libc-alpha
2021-07-13 0:22 ` Michael Hudson-Doyle via Libc-alpha
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 \
--in-reply-to='CAJ8wqtfX2yn721W=hKZTByxBRRPxxGDLOEw8t6+6rfQUb3oGWA@mail.gmail.com' \
--to=libc-alpha@sourceware.org \
--cc=binutils@sourceware.org \
--cc=bug-gnulib@gnu.org \
--cc=fweimer@redhat.com \
--cc=michael.hudson@canonical.com \
/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).