X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C6E243858426
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1694219776;
	bh=UNBpzJynB3ZtTf7X0DEGo0tIjKMVDQtDApxXLQEAQ9I=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=j2fojnQUicHHqAmk6lWrG+0k1UPbu3netzCI45+n62TkHerCC4v2dfhRa/gwMLZWi
	 I/m3yWMdfiOvcHCzN2mZTcGC4vWPbDRuPqWZBomDTI1FB3jgx9jKzOyKTvRMQgoOHi
	 rZf0z7+2KM6y1B+fH8auplshhg4ARYV/t5a9O0Z8=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org B4ED13858D1E
Date: Sat, 9 Sep 2023 09:35:14 +0900
To: cygwin AT cygwin DOT com
Subject: Re: ARG_MAX missing from getconf
Message-Id: <20230909093514.3be884fac1661dc9f9a092b7@nifty.ne.jp>
In-Reply-To: <CANnL4pMk-Y_0hS+z_VzK_Egf4hk2seztJA_b=24iYxf0t=jj2Q@mail.gmail.com>
References: <CANnL4pMrcdfZheDO7_-sR92CtGH5jJVuw=sAJeAtummjhFGqKQ AT mail DOT gmail DOT com>
 <ZPr8KB/MpdMOe2IL AT calimero DOT vinschen DOT de>
 <CANnL4pMk-Y_0hS+z_VzK_Egf4hk2seztJA_b=24iYxf0t=jj2Q AT mail DOT gmail DOT com>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version: 1.0
X-Spam-Status: No, score=-5.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_PASS, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

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 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.

For what purpose do you use ARG_MAX value?
In Linux, ARG_MAX value varies by "ulimit -s xxxx" command.
In my environment, it's 2097152 by default, however, after
ulimit -s 1024
, it will be reduced to 262144.

So, I think it is not good idea to use ARG_MAX value for the
purpose other than its original purpose.

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple