Re: call_once: Work around Cygwin 3.5.3 bug

2024-05-30 Thread Bruno Haible
Hi Jeffrey, > > call_once, being implemented on top of pthread_once in Cygwin, is affected > > by the same bug, and needs a workaround as well. > > Be careful of call_once. Be sure to test it on non-x86 machines. Cygwin exists only for x86. I've run a testdir of all of gnulib on various Linux/

Re: call_once: Work around Cygwin 3.5.3 bug

2024-05-30 Thread Jeffrey Walton
On Thu, May 30, 2024 at 5:38 AM Bruno Haible wrote: > > call_once, being implemented on top of pthread_once in Cygwin, is affected > by the same bug, and needs a workaround as well. Be careful of call_once. Be sure to test it on non-x86 machines. See bugs like

call_once: Work around Cygwin 3.5.3 bug

2024-05-30 Thread Bruno Haible
call_once, being implemented on top of pthread_once in Cygwin, is affected by the same bug, and needs a workaround as well. 2024-05-30 Bruno Haible call_once: Work around Cygwin 3.5.3 bug. * m4/call_once.m4 (gl_FUNC_CALL_ONCE): Require AC_CANONICAL_HOST. On Cygwin