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@sbcglobal.net>
Reply-To: tprince@myrealbox.com
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: GCC 4.1.1?
References: <4540FD95.4030402@cesmail.net>
In-Reply-To: <4540FD95.4030402@cesmail.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.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@gcc.gnu.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/

