[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Undefined use of weak symbols in gnulib

From: Paul Eggert
Subject: Re: Undefined use of weak symbols in gnulib
Date: Mon, 26 Apr 2021 23:50:26 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1

On 4/26/21 10:53 PM, Florian Weimer via Libc-alpha wrote:
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.

Thanks for mentioning this. But in what sense will the modules stop working? I'm a little lost.

glibc 2.34 also defines pthread_once unconditionally, right? So why doesn't code like this:

  if (pthread_mutexattr_gettype != NULL)
    pthread_once (control, callback);

continue to work in 2.34?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]