Bruno's the expert here, though; I hope he has time to weigh in.
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).
- Undefined use of weak symbols in gnulib Florian Weimer
- Re: Undefined use of weak symbols in gnulib Paul Eggert
- Re: Undefined use of weak symbols in gnulib Florian Weimer
- Re: Undefined use of weak symbols in gnulib Paul Eggert
- Re: Undefined use of weak symbols in gnulib Andreas Schwab
- Re: Undefined use of weak symbols in gnulib Florian Weimer
- Re: Undefined use of weak symbols in gnulib Bruno Haible
- Re: Undefined use of weak symbols in gnuli... H.J. Lu
- Re: Undefined use of weak symbols in ... H.J. Lu
- Re: Undefined use of weak symbols... Fangrui Song
- Re: Undefined use of weak symbols in ... Florian Weimer
- Re: Undefined use of weak symbols... Michael Matz
- Re: Undefined use of weak symbols in gnuli... Florian Weimer
- Re: Undefined use of weak symbols in ... Bruno Haible