X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Eliminating -mno-cygwin from gcc? Date: Wed, 31 Jan 2007 12:46:28 -0500 Message-ID: <4C89134832705D4D85A6CD2EBF38AE0FC59E55@PAUMAILU03.ags.agere.com> In-Reply-To: <20070131131337.GA17256@trixie.casa.cgf.cx> References: <20070131131337 DOT GA17256 AT trixie DOT casa DOT cgf DOT cx> From: "Williams, Gerald S \(Jerry\)" To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l0VHklDO022273 Christopher Faylor wrote: > When I was maintaining cygwin's gcc, I often thought about eliminating > -mno-cygwin and just providing a pure mingw cross compiler in the > distribution. I completely agree. Anybody depending on -mno-cygwin can create their own shell wrapper. I personally don't care so much about a deprecation period, as long as it explodes noisily and points me in the right direction three years from now when I try to run an old build script that happens to use it. Big projects really shouldn't be using -mno-cygwin, anyway--the preferred way to do it is to install MinGW compilers and either use MSYS or change your Cygwin path to put MinGW's tools first. How complete of a cross chain were you thinking about supporting? I only installed the compilers and my MinGW bin contains over 60 unique executables--that could mean a fair number of i686-mingw-* programs created (consider GNAT for example). gsw -- 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/