X-Spam-Check-By:	sourceware.org
Message-ID:	<45415EF3.6090709@sbcglobal.net>
Date:	Thu, 26 Oct 2006 18:20:51 -0700
From:	Tim Prince <timothyprince AT sbcglobal DOT net>
Reply-To:	tprince AT myrealbox DOT com
User-Agent:	Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: GCC 4.1.1?
References:	<4540FD95 DOT 4030402 AT cesmail DOT net>
In-Reply-To:	<4540FD95.4030402@cesmail.net>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

M. Edward (Ed) Borasky wrote:
> I'm sure this is a FAQ, but I didn't see it anywhere on line. How long
> before GCC 4.1.1 is available in CygWin, and what can we users do to
> accelerate the progress towards said availability?

Why specifically 4.1.1?  4.2.0 has a lot of advantages.  Not many people 
are testing newer gcc versions under cygwin and posting results to 
gcc_testresults AT gcc DOT gnu DOT org.  Far from sufficient interest to make 
cygwin one of the primary supported targets for gcc.
People probably want to be assured that cygwin-specific bugs have been 
fixed, and see satisfactory results for cygwin modifications of standard 
gcc, such as -mno-cygwin support et al.  If you don't need those 
modifications, you are weloome to build (if necessary) and install the 
newer public versions.
I myself don't see a lot of incentive to keep cygwin up to date until 
64-bit support is available.

--
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/

- Raw text -