delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2007/01/31/12:05:37

X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Matthew Woehlke <mw_triad AT users DOT sourceforge DOT net>
Subject: Re: Eliminating -mno-cygwin from gcc?
Date: Wed, 31 Jan 2007 11:00:57 -0600
Lines: 25
Message-ID: <epqi09$nr8$1@sea.gmane.org>
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> <17393e3e0701310808s2e8e77d9t638d0e90a83c3ecb AT mail DOT gmail DOT com> <epqg4d$h8d$1 AT sea DOT gmane DOT org> <20070131163221 DOT GD19137 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version: 1.0
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20061206 Thunderbird/1.5.0.9 Mnenhy/0.7.4.0
In-Reply-To: <20070131163221.GD19137@trixie.casa.cgf.cx>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Christopher Faylor wrote:
> On Wed, Jan 31, 2007 at 10:29:01AM -0600, Matthew Woehlke wrote:
>> Matt Wozniski wrote:
>>> Before simply ripping out support for it, how about just adding a
>>> message to gcc so that when passed "-mnocygwin" on the command line, it
>>> warns that it's deprecated and will be removed in the near future,
>>> before processing?
>> ...and add a REALLY BIG MESSAGE that, if something breaks, the person to 
>> complain to is the package maintainer and not the Cygwin ML. :-)
> 
> No, if something breaks then the user has to fix it.

I was responding to Corinna's comment "there are many projects out there 
which build environment requires `gcc -mno-cygwin' to work". Maybe these 
are all 'in-house' things? What I meant was to complain to the person 
who decided to use -mno-cygwin and not to us. :-)

Sorry if that wasn't clear.

-- 
Matthew
OFFICER throws a tear gas grenade at you. You start to feel nauseous. 
You need fresh air quickly.
 > OPEN WINDOWS
Sorry, I have a philosophical objection to Microsoft products.


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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019