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.y...@nifty.ne.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
