X-Spam-Check-By:	sourceware.org
Date:	Thu, 1 Feb 2007 15:15:54 +0100 (MET)
From:	Angelo Graziosi <Angelo DOT Graziosi AT roma1 DOT infn DOT it>
To:	cygwin AT cygwin DOT com
Subject:	Re: Eliminating -mno-cygwin from gcc?
Message-ID:	<Pine.OSF.4.21.0702011504020.32267-100000@ax0rm1.roma1.infn.it>
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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:

> 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".


... and if they do not like the name "i686-mingw-gcc", they could create
symbolic links "gcc32 --> i686-mingw-gcc", "g77_32 --> i686-mingw-g77"
etc., so they can "make" their project with "CC=gcc32 make" etc..


I concord with the need to get away the confusing '-mno-cygwin'.

I would suggest of not adopting any work around that reintroduces that
option underhandly...


   Cheers,

         Angelo.      


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