Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Fri, 23 Jun 2000 20:26:46 -0400 To: cygwin AT sourceware DOT cygnus DOT com Cc: scarter AT emware DOT com Subject: Re: make win32 chokes on lone tab Message-ID: <20000623202646.A31818@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: cygwin AT sourceware DOT cygnus DOT com, scarter AT emware DOT com References: <50028CAE26D1D3118C7F00A0CC50D6252D1DB6 AT EMWARESERVER> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <50028CAE26D1D3118C7F00A0CC50D6252D1DB6@EMWARESERVER>; from scarter@emware.com on Fri, Jun 23, 2000 at 05:01:39PM -0600 On Fri, Jun 23, 2000 at 05:01:39PM -0600, Scott Carter wrote: >We were having some real frustrating problems with make, but eventually >(by chance) tracked the problem down to this: If the final (or any) >command in a rule is an "empty command" (as it's referred to in the >documentation)(that is, the line begins with a tab, but is otherwise >empty -- which, in most editors, looks like a blank line), make will >terminate with a STATUS_ACCESS_VIOLATION error. This was very easy to track down. Running the program under gdb immediately uncovered the problem. I will be making a new release of make-3.79-2 shortly. Btw, please do not send email to cygwin-support AT cygnus DOT com. That is for customers who have purchased the cygwin product. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com