Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: cygwin@cygwin.com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: Shankar Unni Subject: Re: GCC Include Paths Date: Thu, 12 Dec 2002 11:14:29 -0800 Lines: 8 Message-ID: <3DF8E015.6040207@cotagesoft.com> References: NNTP-Posting-Host: adsl-64-165-207-59.dsl.snfc21.pacbell.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1039720512 889 64.165.207.59 (12 Dec 2002 19:15:12 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 12 Dec 2002 19:15:12 +0000 (UTC) User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en Vijay Sampath wrote: > I just tried out a line with 20000 characters and it works fine on bash > as an input to GCC. I think that direct Cygwin-to-Cygwin invocation has a higher limit. If you're calling a Cygwin program from a non-Cygwin program (e.g. CMD.EXE), you're still stuck with Windows limits. -- 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/