Simon Josefsson wrote:
> The attached syntax-check rule will help us catch this problem in
> packages.
Yes, it does ;-) It already caught libtool:
https://lists.gnu.org/archive/html/bug-libtool/2024-09/msg2.html
Bruno
Marc Nieper-Wißkirchen wrote:
> You can find some history in [1], especially in the section "Neonatal C".
> [1] http://cm.bell-labs.co/who/dmr/chist.html
Thanks, that explains it!
Am Mo., 2. Sept. 2024 um 13:58 Uhr schrieb Bruno Haible :
> I did:
> > vma-prot: Add tests.
> > * tests/test-vma-prot.c: New file.
> > * modules/vma-prot-tests: New file.
>
> Oops, I forgot some parentheses. (I will never understand why the '&' and
> '|'
> operators, which are mo
I did:
> vma-prot: Add tests.
> * tests/test-vma-prot.c: New file.
> * modules/vma-prot-tests: New file.
Oops, I forgot some parentheses. (I will never understand why the '&' and '|'
operators, which are most meaningful on unsigned integer values, not on
boolean values, have lowe
Bruno Haible writes:
> Simon Josefsson wrote:
>> I fixed the other remaining files with the attached patch.
>
> Thanks for doing this. I now did the same thing in other packages I maintain
> or help maintain.
The attached syntax-check rule will help us catch this problem in
packages.
/Simon
Fro
A few dependency conditions can be improved a little bit:
2024-09-02 Bruno Haible
error, getprogname: Stricter dependency conditions.
* modules/error (Depends-on): Add dependency condition.
* modules/getprogname (Depends-on): Make dependency condition stricter.
On Haiku, I see these test failures:
FAIL: test-futimens
===
../../gltests/test-futimens.h:123: assertion 'get_stat_atime_ns (&st1) ==
get_stat_atime_ns (&st2)' failed
Abort
FAIL test-futimens (exit status: 149)
FAIL: test-utime
../../gltests/test-utime.c:85: a
