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: GCC 4.1.1 Date: Tue, 26 Jun 2007 18:03:16 -0400 Message-ID: <4C89134832705D4D85A6CD2EBF38AE0F01097C08@PAUMAILU03.ags.agere.com> In-Reply-To: References: 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 l5QM3b7L021192 Brian Dessent wrote: > With that out of the way, it's possible to get -mno-cygwin working with gcc4 > just fine, it shouldn't take any patches. You'll of course have to build gcc > again as the MinGW version, and set up some symlinks. See the postinstall of > the gcc package for details. On a related note, is Cygwin's MinGW cross-compiler still switching to the more Gnu-ish convention (i.e., called as i686-pc-mingw-gcc and without -mno-cygwin)? 4 or 5 months ago it sounded like such a change was imminent. We already build i686-pc-mingw-gcc and friends for Linux. I've been debating whether I should build Cygwin versions (or more likely create shell wrappers), which would allow us to transition later without changing our makefiles. If this isn't happening anytime soon, I'd favor building my own to wrappers. (If it's not happening at all, I'd stick to -mno-cygwin.) 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/