X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <48AF03F6.D19BBC3C@dessent.net> Date: Fri, 22 Aug 2008 11:22:46 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Compiling gcc for cygwin References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com NightStrike wrote: > If cygwin ever wants to be able to support newer gcc compilers, > something needs to be done in this area. There are several options, That's a quite a misleading statement to make. Everything is fine for a native 4.4 using 3.4 as the bootstrap compiler. That's the whole point of the three stage bootstrap, to eliminate any influence of the bootstrap compiler on the final compiler. The problem only occurs when you build a 4.4 cross using 3.4 because by definition you can't bootstrap a cross. But even then you're fine if you first bootstrap a recent native to use to build the cross. It's really not the end of the world. Brian -- 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/