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 To: "Charles S. Wilson" Cc: Christopher Faylor , autoconf@gnu.org, cygwin@cygwin.com Subject: Re: Detecting the need for -mwin32 in newer cygwin gcc's References: <20010307161214.A20717@redhat.com> <3AA74730.D4C575FC@ece.gatech.edu> From: Alexandre Oliva Date: 08 Mar 2001 07:48:57 -0300 In-Reply-To: <3AA74730.D4C575FC@ece.gatech.edu> Message-ID: Lines: 26 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Mar 8, 2001, "Charles S. Wilson" wrote: > So, by absorbing AC_PROG_GCC_USES_MWIN32, are you helping the GPL half, > or the proprietary half? > By refusing to absorb it, are you hurting the proprietary half, or the > GPL half? > Both, of course. > Which is more important? Autoconf is about portability across multiple platforms. If you depend on MS-Windows proprietary libraries, there's not much hope for portability. So, why use autoconf, in the first place? If you don't depend on MS-Windows proprietary libraries, then there's no reason for -mwin32. Or am I missing something about the effects of this new -mwin32 flag? -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer aoliva@{cygnus.com, redhat.com} CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org} Free Software Evangelist *Please* write to mailing lists, not to me -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple