X-Spam-Check-By: sourceware.org
Message-ID: <45C38083.50400@users.sourceforge.net>
Date: Fri, 02 Feb 2007 12:18:43 -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: <20070131131337 DOT GA17256 AT trixie DOT casa DOT cgf DOT cx> <45C2BF7D DOT 9060206 AT users DOT sourceforge DOT net> <20070202121553 DOT GA13467 AT trixie DOT casa DOT cgf DOT cx>
In-Reply-To: <20070202121553.GA13467@trixie.casa.cgf.cx>
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

Christopher Faylor wrote:
> I'm not sure that it makes the gcc package that much easier to develop
> since, presumably, we'd be adding a new gcc mingw package which would
> have to be kept in step with the cygwin gcc.

It will be easier because the Cygwin-specific patch will be much cleaner.

Need the gcc and mingw32-gcc maintainers be the same?  These will be two
independent packages, just like the aformentioned possible
i686-linux-gcc package could easily be done by someone else.  It's
possible that the gcc and mingw32-gcc release schedules may not be the
same, due to individual requirements of each.

> Don't forget that Cygwin itself uses it.  That would require a change in
> Cygwin's build, which I am, of course, willing to do.

But you and Corinna won't be caught off-guard by this change. :-)  Most
others might, but I'm not convinced that it's our problem.


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

iD8DBQFFw4CCpiWmPGlmQSMRCH9QAKDgIv4jbXr0ZES5Uo69wxCFCNhPdwCeMwUk
QJi2y6TE4w80M65hx6GzLdE=
=D2jB
-----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/