On Thu, Sep 29, 2022 at 05:45:28PM +0200, Uli Schlachter wrote:
> Hi,
>
> Am 29.09.22 um 06:27 schrieb Keith Packard:
> > Alan Coopersmith writes:
> >
> > > Does anyone disagree?
> >
> > Yeah, synchronizing with xcb seems 'obviously right. The only question
> > I've got is that in 2022, should
Alan Coopersmith writes:
> I'm not familiar with the runtime linkers on all platforms, but I know at
> least
> on Solaris, lazy loading won't load the library until the first reference to
> it
> is made (or a search needs to be made for a reference that doesn't have direct
> binding
Hi,
Am 29.09.22 um 06:27 schrieb Keith Packard:
Alan Coopersmith writes:
Does anyone disagree?
Yeah, synchronizing with xcb seems 'obviously right. The only question
I've got is that in 2022, should xcb ever use stubs for the thread functions?
No, it shouldn't. That's why since 2017,
Hi,
Am 29.09.22 um 02:29 schrieb Alan Coopersmith:
[...]
Which in hindsight, sounds a lot like that bug 162 linked above - the
libX11
xlib_ctor would call XInitThreads() at library load time, which would
use the
stubs to fake initializing the mutexes, and then libxcb would be loaded
later
On 9/29/22 08:44, Uli Schlachter wrote:
Hi,
Am 29.09.22 um 02:29 schrieb Alan Coopersmith:
[...]
Which in hindsight, sounds a lot like that bug 162 linked above - the libX11
xlib_ctor would call XInitThreads() at library load time, which would use the
stubs to fake initializing the mutexes,
