From: Paul Eggert <eggert@cs.ucla.edu>
To: Florian Weimer <fweimer@redhat.com>,
Joseph Myers <joseph@codesourcery.com>
Cc: Carlos O'Donell <carlos@redhat.com>,
libc-alpha@sourceware.org, bug-gnulib@gnu.org,
Bruno Haible <bruno@clisp.org>
Subject: Re: Undefined use of weak symbols in gnulib
Date: Tue, 27 Jul 2021 16:38:46 -0700 [thread overview]
Message-ID: <84fa7f6b-cb0a-8154-7153-b183423cbac0@cs.ucla.edu> (raw)
In-Reply-To: <877dhbbjc8.fsf@oldenburg.str.redhat.com>
On 7/27/21 1:19 PM, Florian Weimer wrote:
>> So if there's any change regarding LIBPTHREAD_SO, I think the natural one
>> would be to define it to LIBC_SO (I hope the dlopen/dlsym case works
>> regardless of whether that change is made or not).
> That is in an interesting idea. I like it.
Me too.
> It doesn't help with Bruno's use case, detecting the integrated
> libpthread with the preprocessor.
It might be good enough for that use case, if the detection of
LIBPTHREAD_SO==LIBC_SO can be done at 'configure' time instead of at
preprocessor time. (Bruno would be a better person to opine on this.)
next prev parent reply other threads:[~2021-07-27 23:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 5:53 Florian Weimer
2021-04-27 6:50 ` Paul Eggert
2021-04-27 6:58 ` Florian Weimer
2021-04-27 7:13 ` Paul Eggert
2021-04-27 7:24 ` Andreas Schwab
2021-04-27 11:06 ` Florian Weimer
2021-04-28 0:09 ` Bruno Haible
2021-04-28 2:10 ` H.J. Lu
2021-04-28 2:13 ` H.J. Lu
2021-05-05 20:31 ` Fangrui Song
2021-04-28 8:35 ` Florian Weimer
2021-04-28 13:15 ` Michael Matz
2021-04-28 7:44 ` Florian Weimer
2021-04-28 14:48 ` Bruno Haible
2021-04-28 17:44 ` Florian Weimer
2021-07-17 14:38 ` Bruno Haible
2021-07-17 14:55 ` Florian Weimer
2021-07-17 16:39 ` Bruno Haible
2021-07-27 20:02 ` Joseph Myers
2021-07-27 20:19 ` Florian Weimer
2021-07-27 23:38 ` Paul Eggert [this message]
2021-04-27 23:22 ` Bruno Haible
2021-04-27 23:47 ` Bruno Haible
2021-04-28 7:57 ` Florian Weimer
2021-04-28 14:40 ` Bruno Haible
2021-04-28 17:43 ` Florian Weimer
2021-04-29 15:15 ` Bruno Haible
2021-04-30 9:55 ` Florian Weimer
2021-04-29 6:33 ` Ben Pfaff
2021-05-03 1:44 ` Alan Modra
2021-07-12 10:04 ` Michael Hudson-Doyle
2021-07-12 15:03 ` Florian Weimer
2021-07-12 15:30 ` Matthias Klose
2021-07-12 15:37 ` Florian Weimer
2021-07-13 0:22 ` Michael Hudson-Doyle
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=84fa7f6b-cb0a-8154-7153-b183423cbac0@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.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).