On musl libc, test-vasnwprintf-posix fails. This is due to two musl libc bugs:
https://www.openwall.com/lists/musl/2023/03/19/1
https://www.openwall.com/lists/musl/2023/03/20/1
As a workaround, on this platform, vasnwprintf needs to
- avoid %n,
- do the padding itself, instead of leaving i
The vasnwprintf implementation and tests depend on a few wide-character string
functions from . This patch adds the dependencies.
It also depends on 'swprintf'; to be added later.
2023-03-19 Bruno Haible
vasnwprintf: Fix module dependencies.
* modules/vasnwprintf (Depends-on)
On Sun, Mar 19, 2023 at 4:12 PM Paul Eggert wrote:
> On 2023-03-19 13:44, Jim Meyering wrote:
> > I've pushed your change along with the attached.
> > I'll probably create another snapshot today.
>
> Thanks. I also installed a minor dfa.c change in Gnulib yesterday to
> pacify Oracle Solaris Studi
On 2023-03-19 13:44, Jim Meyering wrote:
I've pushed your change along with the attached.
I'll probably create another snapshot today.
Thanks. I also installed a minor dfa.c change in Gnulib yesterday to
pacify Oracle Solaris Studio. No big deal since 'grep' builds OK anyway.
I also ran into
Bruno Haible writes:
> Hi Sam,
Hi Bruno,
>
>> The test-pthread-cond test fails for me.
>>
>> gnulib-tests/test-pthread-cond.log doesn't have much detail:
>> ```
>> Starting test_pthread_cond_wait ... OK
>> Starting test_pthread_cond_timedwait ...FAIL test-pthread-cond (exit
>> status: 134)
>>
I spent a while trying to work out why I was getting CVS errors from the
script for GNU a2ps, and I realised that the problem was that a2ps's manual
wasn't online yet. This causes confusing error messages when the "manual"
subdirectory isn't online, and cvs can't find a CVS directory and hence
CVSR
> * MODULES.html.sh: Add some recently-added modules.
Thanks, Paul.
> Assuming MODULES.html.sh is still useful,
> at some point a more-complete update should be done.
While I refer more people to the gnulib.texi documentation than to
MODULES.html, I still think that MODULES.html is useful to get
Hi Sam,
> The test-pthread-cond test fails for me.
>
> gnulib-tests/test-pthread-cond.log doesn't have much detail:
> ```
> Starting test_pthread_cond_wait ... OK
> Starting test_pthread_cond_timedwait ...FAIL test-pthread-cond (exit
> status: 134)
> ```
Is it reproducible?
I'm asking because o
