Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com From: Chris Faylor Date: Thu, 5 Oct 2000 18:44:06 -0400 To: cygwin-developers AT sources DOT redhat DOT com Subject: Re: Command line length is too long for winsup/cisnatll to build. Message-ID: <20001005184406.A24113@cygnus.com> Reply-To: cygwin-developers AT sources DOT redhat DOT com Mail-Followup-To: cygwin-developers AT sources DOT redhat DOT com References: <20001005224251 DOT 7393 DOT qmail AT web110 DOT yahoomail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <20001005224251.7393.qmail@web110.yahoomail.com>; from earnie_boyd@yahoo.com on Thu, Oct 05, 2000 at 03:42:51PM -0700 On Thu, Oct 05, 2000 at 03:42:51PM -0700, Earnie Boyd wrote: >--- Brian Keener wrote: >> Jeez I'm glad you guys found that. Last couple times I updated setup >> from the cvs I got that and ended up deleting my build and rebuilding and >> then this last time I was working on choose.cc and thought it was >> something I was doing. I thought it might be an update versus my >> timestamp problem or something. >> >> Glad you found it and I'll be sure to get that update. >> > >I suppose it would be nice when the Cygwin core team updates they post to the >list what they fixed. I'm on the cygwin-patches list and didn't see anything >come through on that either. Subscribe to cygwin-cvs AT sources DOT redhat DOT com. Then you'll see every patch that is made to the repository. Or, just put a 'cvs update' in a cron process to run hourly. cgf