On 2026-01-10 15:04, Jon Turney wrote:
On 10/01/2026 17:01, Brian Inglis via Cygwin-apps wrote:
Hi folks,
It appears that upstream package autoconf versions can now have git-like
suffixes so are no longer always only integer patch levels:
$ gettext-0.26-1.noarch/src/gettext-0.26/configure --version
gettext configure package
generated by GNU Autoconf 2.72.85-f3b0a
/usr/share/cygport/cygclass/autotools.cygclass: line 724: [: 85-f3b0a: integer
expression expected
/usr/share/cygport/cygclass/autotools.cygclass: line 738: [: 85-f3b0a: integer
expression expected
Huh.
Yeah, we need to handle that properly.
I think explicitly setting AUTOCONF_VERSION to e.g. 2.72 should work as a
temporary workaround.
Thanks Jon,
Nice idea!
some mitigation appears required as under mingw package build, stdout is
closed, and the rest of the compile log and subsequent logs do not appear: see
GH Scallywag job 10992 rerunning as 10994!
Yeah, that seems like a secondary effect.
Uh, I'm unclear what's happening there to make it hang there with no output, and
can't immediately reproduce it locally.
Do you have some more information which leads to the "stdout is closed" theory,
or is that just speculation?
Only happens so far on mingw...gettext build and both times had same effect but
different amount of output in log (buffering amount) nearing end of config, as
also under GH Scallywag; I also run my own build log time stamper so I can spot
hangs during builds.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut
-- Antoine de Saint-Exupéry
