Ok, I guess that makes sense.

My worry was some './configure' script determining that the build
environment is somehow not 'sane'. At least for the limited set of programs
that I use under cygwin, I have set up my CI to now watch for changes in
which binaries are present. Nothing obviously significant in that history
so far.

At this point, from comparing with my previous CI results, I am guessing
this doesn't affect me, aside from adding an exception to my test case for
this specifically. Might be better to get closer to the usual Linux
behavior I am familiar with, of a much higher, valid, ARG_MAX value.

On Fri, Sep 8, 2023 at 6:49 AM Corinna Vinschen <corinna-cygwin@cygwin.com>
wrote:

> On Sep  8 00:14, Matthew "mirage335" Hines via Cygwin wrote:
> > Really hope other Cygwin packages will not be broken because 'ARG_MAX' is
> > now undefined in 'getconf' output. Caught this in a CI test for a rather
> > large shell script.
> >
> >
> https://github.com/mirage335-colossus/ubiquitous_bash/blob/master/structure/installation.sh#L385
>
> Please read this, this is supposed to explain the new ARG_MAX
> behaviour sufficiently:
>
> https://cygwin.com/pipermail/cygwin/2023-August/254352.html
>
>
> Corinna
>