Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: John Williams Subject: Re: Bug in Cygwin bash? Date: Thu, 03 Apr 2003 12:58:23 +1000 Lines: 25 Message-ID: References: <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030402183025 DOT 02a99358 AT pop3 DOT cris DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en In-Reply-To: <5.2.0.9.2.20030402183025.02a99358@pop3.cris.com> Randall R Schulz wrote: > John, > > Yes, there's a limitation on the total volume of argument strings. All > Unix systems have such a limit and so does Cygwin. The limits vary from > system to system, though POSIX dictates a minimum value for this limit. Anybody know the standard Cygwin limit off the top of their head? I'm guessing 32K, given what I saw with mkdep > For cases where the total list of files can be processed in pieces, the > xargs command will do the divvying up for you, invoking the command as > many times as needed to process all the arguments it reads from standard > input. Check it out--it should be in your script-writing repertoire. Yup - I used xargs in my solution to this problem. It seems not many people build linux kernels under cygwin - I think if they did, this issue I've found would have been reported earlier, because it's the first step in the kernel configuration process. Thanks for your reply, John -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/