public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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 19:02:39 -0400	[thread overview]
Message-ID: <CANnL4pM5pM=DCNWa4LKCfSe-wtm_b0DDfuy-wki98dS6j2xcDQ@mail.gmail.com> (raw)
In-Reply-To: <ZPsJKZjc1woHSZFu@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]

Ok, excellent, thank you, good to know.

On Fri, Sep 8, 2023 at 7:44 AM Corinna Vinschen <corinna-cygwin@cygwin.com>
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 '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.
>
> We just don't have a maximum except an out of resources situation.  A
> standard-conformant application must deal with any sysconf variable
> denoting a limit to return -1, i. e., "no limit".
>
> Corinna
>

  reply	other threads:[~2023-09-08 23:02 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
2023-09-08 11:44     ` Corinna Vinschen
2023-09-08 23:02       ` Matthew "mirage335" Hines [this message]
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='CANnL4pM5pM=DCNWa4LKCfSe-wtm_b0DDfuy-wki98dS6j2xcDQ@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).