Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Thu, 19 Oct 2000 13:31:54 -0400 From: Christopher Faylor To: cygwin@sources.redhat.com Subject: Re: FAQ about make Message-ID: <20001019133153.B785@cygnus.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: cygwin@sources.redhat.com References: <20001019130723.6247.qmail@web112.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <20001019130723.6247.qmail@web112.yahoomail.com>; from earnie_boyd@yahoo.com on Thu, Oct 19, 2000 at 06:07:23AM -0700 On Thu, Oct 19, 2000 at 06:07:23AM -0700, Earnie Boyd wrote: >--- Chris Faylor wrote: >> On Wed, Oct 18, 2000 at 10:14:57PM +0100, David Starks-Browning wrote: >> >Wait, I'm confused now. Red Hat will ship with the environment >> >variable MAKE_MODE=win32 set? Or will ship a version of make where >> >--win32 behavior is the default? >> >> The latter. > >Would it help if we voiced complaint somewhere within Redhat? What >reasoning is behind this? The reasoning is that we have customers who are used to MAKE_MODE=win32 and rely on it. One of our biggest customers uses make, gcc, etc. only as a native windows solution. They don't care about mount tables or cygwin at all. They want to be able to say: d:\foo\bar.exe : gcc -o d:\foo\bar.exe c:\bob\sproing.c and not have to worry about specifying MAKE_MODE=win32. Complaining to Red Hat wouldn't help with this. There is too much entrenched use of the win32 stuff with the old Cygnus customers. I believe that eCos might even use it in their makefiles, in fact. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com