X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii; format=flowed Message-id: <47CF1F9E.4070608@dnasoft.com> Date: Wed, 05 Mar 2008 17:33:02 -0500 From: Francois Colbert User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920 To: cygwin AT cygwin DOT com Subject: Re: Setting MAKE_MODE breaks make.exe References: <47CCAFFA DOT 3090307 AT dnasoft DOT com> In-reply-to: <47CCAFFA.3090307@dnasoft.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Well... setting MAKE_MODE to "win32" also makes the process stop with the same error message, without even reading the Makefile. It seems that only "unix" is accepted, and there's already a "--unix" parameter that does the same thing. I'm talking about an already existing Makefile, here. One that expects MAKE_MODE to be set to something else than "unix", for its own purpose, and doesn't care about windows-style paths. The --unix flag is a much better option, in my opinion, because it makes "make" depend only on the way it's invoked, instead of relying on environment variables that can vary greatly from one environment to another. Reacting to MAKE_MODE just makes Cygwin's "make" more different and less useful when porting a development environment to Windows/Cygwin. fc -- 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/