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: <3EA7E46D.4080609@fangorn.ca> Date: Thu, 24 Apr 2003 09:19:41 -0400 From: Mark Blackburn Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4a) Gecko/20030401 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: 1.3.12 & XP command line limit exceeded References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Brian Post wrote: > We are using Cygwin to host Sony's PS2 version of the GCC compiler to > build our PS2 game. > > I use ee-ar to build some libraries and have found a problem where a > command line length of > 32K fails with an error. I have included in > 4Cygwin.zip because of list 100000 bytes limit an example which works & > one that fails & the results of cygcheck. The working command line is > 21941 characters long while the one that fail is 34651 characters long. > I tried making it less than 32K but that didn't work. > > > Different environments have different command line length limits. I'm not sure what cygwin's is. I believe POSIX only requires 2k though and you're well over that so I wouldn't expect a cygwin patch if I were you. You might be better off working around it: for i in $(OBJS) ; do ee-ar -r $$i; done (if this doesn't mess up /bin/sh) or if your project is somewhat organized ee-ar -r $(FOO_OBJS) ee-ar -r $(BAR_OBJS) etc. assuming all of your subgroups of objects won't violate any limits. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/