X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 3 Mar 2008 21:36:07 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Setting MAKE_MODE breaks make.exe Message-ID: <20080304023606.GA13920@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <47CCAFFA.3090307@dnasoft.com> <47CCB14F.15BA2A01@dessent.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47CCB14F.15BA2A01@dessent.net> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Mon, Mar 03, 2008 at 06:17:51PM -0800, Brian Dessent wrote: >Francois Colbert wrote: > >> I think that a simple warning message (or no message at all?) and >> *normal* continuation of the process (ie: no abort) would be sufficient >> since "make" doesn't seem to be using this variable anymore. Its only > >I think the idea is that if you have a Makefile that expects to set >MAKE_MODE to "win32" and use c:/foo/bar-style paths, it will fail >catastrophically anyway, so there's no point in continuing. That's correct. This behavior is not going to change. cgf -- 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/