X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <4C89134832705D4D85A6CD2EBF38AE0F01097C08 AT PAUMAILU03 DOT ags DOT agere DOT com> Subject: RE: GCC 4.1.1 Date: Tue, 26 Jun 2007 23:21:25 +0100 Message-ID: <00d801c7b840$55ce0010$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <4C89134832705D4D85A6CD2EBF38AE0F01097C08@PAUMAILU03.ags.agere.com> 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 On 26 June 2007 23:03, Williams, Gerald S (Jerry) wrote: > 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. Yes, this is still my plan: package an entirely independent and separate mingw-targeted cross-compiler, drop mno-cygwin support from cygwin native gcc. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/