The native builds on MacOS and Linux work with the tip of master with some 
fixes in the regression.
The fixes are due to line breaks around a dot. Words like DATE.TIME are now not 
broken around the
dot. I have made the fixes already.

The Crossbuild works with a gnulib version from end of last year, but later 
versions show this
problem:

../pspp/src/data/any-reader.c: In function 'any_reader_open':
../pspp/src/data/any-reader.c:119:21: error: 'const struct any_reader_class' 
has no member named 'rpl_open'
  119 |         return class->open (handle);
      |                     ^~
../pspp/src/data/any-reader.c:127:34: error: 'const struct any_reader_class' 
has no member named 'rpl_open'
  127 |       return dataset_reader_class.open (handle);
      |                                  ^
../pspp/src/data/any-reader.c:106:7: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
  106 |       {
      |       ^
../pspp/src/data/any-reader.c:122:5: note: here
  122 |     case FH_REF_INLINE:
      |     ^~~~

Latest from the stable-202507 branch shows the same problem.
Latest from the stable-202501 branch works. That is

commit 11ec314e8d35829efac53b7a55a0a63fcabfadf1 (HEAD, origin/stable-202501)
Author: Paul Eggert <[email protected]>
Date:   Mon Sep 1 11:25:00 2025 -0700

I pushed that version together with the regression fixes. Going further up
needs more work in the crossbuild for windows and I do not know what
needs to be changed.

> Am 15.09.2025 um 17:53 schrieb Ben Pfaff <[email protected]>:
> 
> I think the first step is to upgrade gnulib. What commit should we upgrade 
> to? Is the tip of master on gnulib OK?
> 
> On Mon, Sep 15, 2025 at 5:55 AM Friedrich Beckmann 
> <[email protected]> wrote:
> Hi John, hi Ben,
> 
> 2.0.1 was released in March 2024. Maybe it is time to make new release?
> 
> I fixed some bugs from the bugtracker. At the moment I try to
> update the Windows dependencies such that the crossbuild works on Trixie.
> That needs an update of gnulib also.
> 
> Regards
> 
> Fritz
> 


Reply via email to