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 Message-Id: <5.2.0.9.2.20021212105727.0311be48@pop3.cris.com> X-Sender: rrschulz AT pop3 DOT cris DOT com Date: Thu, 12 Dec 2002 11:00:53 -0800 To: cygwin AT cygwin DOT com From: Randall R Schulz Subject: RE: GCC Include Paths In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Vijay, I guess I was misled by this: /usr/include/limits.h:#define _POSIX_ARG_MAX 4096 /usr/include/sys/syslimits.h:#define ARG_MAX 65536 /* max bytes for an exec function */ Furthermore, "/usr/include/limits.h" bears a Red Hat copyright and is specifically marked as a "part of Cygwin," while "/usr/include/sys/syslimits.h" bears a "Regents of the University of California" copyright. Thus I assumed the former was more authoritative. Sorry (again) for the misinformation. Randall Schulz Mountain View, CA USA At 10:53 2002-12-12, Vijay Sampath wrote: >Randall, > >I just tried out a line with 20000 characters and it works fine on bash >as an input to GCC. At this point I gave up trying to increase the >length to find out the limit. Whatever the bash limit is, it is >definitely greater than a windows shell. Of course, if you are invoking >a bat file or some such thing from a cygwin shell then you will be >bounded by the windows limit. Therefore Allan, I suggest trying to move >to a "pure" cygwin enviroment, if there is such a thing. > >Thanks, > >Vijay -- 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/