X-Spam-Check-By: sourceware.org
Message-ID: <17393e3e0701310808s2e8e77d9t638d0e90a83c3ecb@mail.gmail.com>
Date: Wed, 31 Jan 2007 11:08:18 -0500
From: "Matt Wozniski" <godlygeek AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Eliminating -mno-cygwin from gcc?
In-Reply-To: <20070131154054.GC19137@trixie.casa.cgf.cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20070131131337 DOT GA17256 AT trixie DOT casa DOT cgf DOT cx> 	 <45C0971E DOT 4080305 AT byu DOT net> 	 <20070131132700 DOT GA3478 AT implementation DOT labri DOT fr> 	 <20070131133102 DOT GA17405 AT trixie DOT casa DOT cgf DOT cx> 	 <20070131134842 DOT GU27843 AT calimero DOT vinschen DOT de> 	 <050901c74547$76f60e20$2e08a8c0 AT CAM DOT ARTIMI DOT COM> 	 <20070131154054 DOT GC19137 AT trixie DOT casa DOT cgf DOT cx>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 1/31/07, Christopher Faylor wrote:
> I feel pretty strongly about this.  I really don't think this option should
> exist.  It's unlike every other gcc port on the planet.
>
> cgf

Before simply ripping out support for it, how about just adding a
message to gcc so that when passed "-mnocygwin" on the commandline, it
warns that it's deprecated and will be removed in the near future,
before processing?  Or, better yet, for perhaps one major version,
have gcc warn that "-mnocygwin" is deprecated, and then just call
"execle" to run i686-mingw-gcc with the other arguments?  (Assuming
that the arguments would be compatible).  If cygwin's gcc has been
this nonstandard for so many years, what's another change to slowly
phase out this 'feature'?  While I agree that it wasn't a good feature
to add in the first place, I think that removing it without at least a
deprecation warning for a version or two will flood the mailing list
with traffic by people who didn't realize that something they used was
being phased out until they upgraded and things just "broke".

--
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/