It's having trouble because Savannah's Git service is flaky, but I'll keep
trying.

On Mon, Sep 15, 2025 at 12:51 PM Ben Pfaff <[email protected]> wrote:

> Triggered.
>
> On Mon, Sep 15, 2025 at 12:49 PM Friedrich Beckmann <
> [email protected]> wrote:
>
>> I just pushed the changes for the Windows build.
>>
>>
>> https://cgit.git.savannah.gnu.org/cgit/pspp.git/commit/?id=47e1e5ba823e79068a609c465c4d57bced197658
>>
>> Can you trigger a tarball? I will try your changes to see if
>> the tip gnulib then works on the crossbuild.
>>
>> > Am 15.09.2025 um 20:30 schrieb Ben Pfaff <[email protected]>:
>> >
>> > On Mon, Sep 15, 2025 at 9:37 AM Friedrich Beckmann <
>> [email protected]> wrote:
>> > 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:
>> >       |     ^~~~
>> >
>> > If you have time to try it, these should be easily fixable by adding
>> parentheses:
>> > (class->open) and (dataset_reader_class.open).  I'll try to find time
>> to fix them
>> > myself if you can't.
>>
>>

Reply via email to