From: "Matthew \"mirage335\" Hines" <spamfreemirage335@gmail.com>
To: cygwin@cygwin.com, Matthew mirage335 Hines <spamfreemirage335@gmail.com>
Subject: Re: ARG_MAX missing from getconf
Date: Fri, 8 Sep 2023 07:36:48 -0400 [thread overview]
Message-ID: <CANnL4pMk-Y_0hS+z_VzK_Egf4hk2seztJA_b=24iYxf0t=jj2Q@mail.gmail.com> (raw)
In-Reply-To: <ZPr8KB/MpdMOe2IL@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
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
>
next prev parent reply other threads:[~2023-09-08 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 4:14 Matthew "mirage335" Hines
2023-09-08 10:49 ` Corinna Vinschen
2023-09-08 11:36 ` Matthew "mirage335" Hines [this message]
2023-09-08 11:44 ` Corinna Vinschen
2023-09-08 23:02 ` Matthew "mirage335" Hines
2023-09-09 0:35 ` Takashi Yano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANnL4pMk-Y_0hS+z_VzK_Egf4hk2seztJA_b=24iYxf0t=jj2Q@mail.gmail.com' \
--to=spamfreemirage335@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).