X-Spam-Check-By: sourceware.org
Message-ID: <45C69F2F.2060300@users.sourceforge.net>
Date: Sun, 04 Feb 2007 21:06:23 -0600
From: "Yaakov (Cygwin Ports)" <yselkowitz AT users DOT sourceforge DOT net>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Eliminating -mno-cygwin from gcc.
References: <020d01c748b4$62d8b170$2e08a8c0 AT CAM DOT ARTIMI DOT COM>
In-Reply-To: <020d01c748b4$62d8b170$2e08a8c0@CAM.ARTIMI.COM>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dave Korn wrote:
> 
>   There have been no serious objections, so I think we should go ahead.
> Perhaps we should replace the gcc, g++, g77 etc. drivers with shell scripts
> that look for -mno-cygwin on the command line and redirect to
> i686-pc-mingw-{gcc,g++,etc} or to i686-pc-cygwin-{gcc,g++,etc}, just to make
> life easier for the backwardly-compatible, but I don't see any reason not to
> go ahead and remove the option from the driver.

Will using shell wrappers noticably slow down calls to gcc?  Or should
we just start explicitly calling i686-pc-cygwin-gcc instead?  (FWIW
Gentoo does the equivalent of the latter.)


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFxp8vpiWmPGlmQSMRCKmkAKCMkLBDBYZ+P8NGLo7eff6+owmvsgCgsDh5
FTvd4ddzyI4MObGrHkRT7ds=
=TTvw
-----END PGP SIGNATURE-----

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