Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Thu, 8 Mar 2001 11:56:58 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
Cc: Alexandre Oliva <oliva AT lsd DOT ic DOT unicamp DOT br>, autoconf AT gnu DOT org,
        cygwin AT cygwin DOT com
Subject: Re: Detecting the need for -mwin32 in newer cygwin gcc's
Message-ID: <20010308115658.B3813@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>,
	Alexandre Oliva <oliva AT lsd DOT ic DOT unicamp DOT br>, autoconf AT gnu DOT org,
	cygwin AT cygwin DOT com
References: <20010307161214 DOT A20717 AT redhat DOT com> <orn1axvuu4 DOT fsf AT guarana DOT lsd DOT ic DOT unicamp DOT br> <3AA74730 DOT D4C575FC AT ece DOT gatech DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <3AA74730.D4C575FC@ece.gatech.edu>; from cwilson@ece.gatech.edu on Thu, Mar 08, 2001 at 03:47:44AM -0500

On Thu, Mar 08, 2001 at 03:47:44AM -0500, Charles S. Wilson wrote:
>Alexandre Oliva wrote:
>> 
>> On Mar  7, 2001, Christopher Faylor <cgf AT redhat DOT com> wrote:
>> 
>> > Basically, I think we need something like a AC_PROG_GCC_USES_MWIN32.
>> 
>> I have mixed feelings about having this macro in autoconf.  On one
>> hand, it would be kind of promoting the use of proprietary software.
>
>Speaking as a cygwin user *not* affiliated with Cygnus/Red Hat, cygwin
>is sortof schizophrenic.  On one hand, it is a totally free (speech &
>beer, libre' and gratis), GPL'ed, software platform.  On the other hand,
>it's also distributed with a proprietary license. If a developer whose
>product depends on cygwin is content to opensource his product, then he
>can use and distribute cygwin under its GPL license and we all win ---
>more libre' software for everyone.  Otherwise, the developer can
>negotiate with Cygwin for a proprietary license, and keep his own source
>closed.  Not ideal, certainly, but I've got no problem with Cygwin/Red
>Hat "punishing" folks that want to stay closed, while making a little
>money on it.  That helps those of us on the libre' side -- imposing a
>"tax" on closed-source development encourages free (libre')
>alternatives.
>
>So, by absorbing AC_PROG_GCC_USES_MWIN32, are you helping the GPL half,
>or the proprietary half?

This doesn't help "the proprietary half" very much at all since we have
control over what we distribute and are technically capable of modifying
the configure scripts to handle the -mwin32 option.

>By refusing to absorb it, are you hurting the proprietary half, or the
>GPL half?
>
>Both, of course.
>
>Which is more important?

Even if "the proprietary half" was something that Red Hat was concerned
about, I don't see why this matters.  autoconf accomodates all manners
of C compilers from all manner of vendors.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple