Paul Eggert wrote:
> > In detail, we have dependency chains
> > exclude -> regex -> lock -> once -> pthread-once
> > nstrftime -> localename-unsafe-limited -> getlocalename_l-simple -> lock
> > -> once -> pthread-once
> > regex -> lock -> once -> pthread-once
> >
> > Here, in fact, the depe
On 2025-02-22 10:02, Bruno Haible wrote:
The latest release already contains some multithreading
support already:
That was inadvertent.
When you intersect the resulting list with the gnulib_modules defined in
diffutils/bootstrap.conf, the result is:
exclude
nstrftime
regex
In detail, we
> 2025-02-22 Bruno Haible
>
> * lib/getlocalename_l.c: Most code moved to
> lib/getlocalename_l-unsafe.c.
After this change, I get a compilation error on OpenBSD (and presumably
also AIX):
cc -DHAVE_CONFIG_H -DNO_XMALLOC -I. -I../../lib -I.. -I. -I../../lib -I..
-I../.. -DIN_LI
diffutils-3.11/lib/glthread:
...
> The first function I found was hard_locale. What's the
> recommended way to use hard_locale in a single-threaded app, without
> pulling in the thread library part of Gnulib?
'hard-locale' relies on 'setlocale-null'. Th
I tried to update GNU diffutils to the latest Gnulib, and found that
this dragged in a bunch of stuff about multithreading that diffutils
doesn't need. The first function I found was hard_locale. What's the
recommended way to use hard_locale in a single-threaded app, without
pull
