From: Paul Eggert <eggert@cs.ucla.edu>
To: Florian Weimer <fweimer@redhat.com>
Cc: bug-gnulib@gnu.org, libc-alpha@sourceware.org, binutils@sourceware.org
Subject: Re: Undefined use of weak symbols in gnulib
Date: Tue, 27 Apr 2021 00:13:56 -0700 [thread overview]
Message-ID: <8fcd3e22-544c-c610-af40-927286a6be5b@cs.ucla.edu> (raw)
In-Reply-To: <87czugp61v.fsf@oldenburg.str.redhat.com>
I'm still not quite following, but the message I'm getting is "don't
mess with dynamic detection of whether the pthread functions are linked
in, because there's no way to do it reliably." If so, I suppose Gnulib
will have to require pthread to be linked into all libraries that use
any of these functions, which has some negative consequences (at least
for glibc 2.33 and earlier).
Bruno's the expert here, though; I hope he has time to weigh in.
next prev parent reply other threads:[~2021-04-27 7:14 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 [this message]
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
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=8fcd3e22-544c-c610-af40-927286a6be5b@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=binutils@sourceware.org \
--cc=bug-gnulib@gnu.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).