On Fri, 8 Sep 2023 07:36:48 -0400
"Matthew \"mirage335\" Hines wrote:
> 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 t
Ok, excellent, thank you, good to know.
On Fri, Sep 8, 2023 at 7:44 AM Corinna Vinschen
wrote:
> On Sep 8 07:36, Matthew "mirage335" Hines via Cygwin wrote:
> > Ok, I guess that makes sense.
> >
> > My worry was some './configure' script determining that the build
> > environment is somehow not
On Sep 8 07:36, Matthew "mirage335" Hines via Cygwin wrote:
> 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 wat
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 signifi
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/m
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
--
Problem reports: https:/
6 matches
Mail list logo