X-Spam-Check-By: sourceware.org
Date: Thu, 1 Feb 2007 07:14:08 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Eliminating -mno-cygwin from gcc?
Message-ID: <20070201121408.GA29751@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <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> <Pine DOT GSO DOT 4 DOT 63 DOT 0701311917170 DOT 4318 AT access1 DOT cims DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.63.0701311917170.4318@access1.cims.nyu.edu>
User-Agent: Mutt/1.5.11
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 Wed, Jan 31, 2007 at 07:24:50PM -0500, Igor Peshansky wrote:
>On Wed, 31 Jan 2007, 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 don't mind adding a deprecated feature but I think some kind of
>> optional wrapper script eliminates the need.
>
>I agree, except that some people invoke Cygwin's gcc from non-Cygwin
>programs, which would present a problem if it were a shell script.
>Perhaps we should add some option preprocessing to the gcc executable
>itself (which would exec the cross-gcc if -mno-cygwin is present)?

Argh.  The whole point of this is to eliminate the abomination that is
-mno-cygwin from gcc itself.

If people are calling gcc from non-cygwin apps, then I don't think I
care too much.  We can also provide a sed script to change "gcc -mno-cygwin"
to "i686-mingw-gcc".

cgf

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