X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Brian Salter-Duke Subject: Re: Compiling gcc for cygwin Date: Mon, 1 Sep 2008 23:06:04 +0000 (UTC) Lines: 30 Message-ID: References: <48AF03F6 DOT D19BBC3C AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: slrn/0.9.9 (CYGWIN_NT-5.1) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Fri, 22 Aug 2008 11:22:46 -0700, Brian Dessent wrote: > 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 Indeed. gcc 4.4 works fine. I have the version that comes with gfortran. Is it likley any time soon that gcc4 and gfortran come as a standard cygwin package. Apologies if I missed this. Another Brian. -- Brian Salter-Duke Melbourne, Australia My real address is b_duke(AT)bigpond(DOT)net(DOT)au Use this for reply or followup. Registered Linux user 287938. Cygwin for Linux on PCs. -- 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/