X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: Date: Tue, 18 Mar 2008 05:42:23 -0400 From: NightStrike To: tprince AT computer DOT org, cygwin AT cygwin DOT com Subject: Re: gmp/mpfr status In-Reply-To: <47DF532B.7060701@sbcglobal.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47DF532B DOT 7060701 AT sbcglobal DOT net> X-IsSubscribed: yes 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 3/18/08, Tim Prince wrote: > I've been building gcc 4.3 and 4.4 with mpfr upgraded to 2.3.1, taking the > gmp provided by cygwin. gcc build doesn't complain about mpfr 2.3.0 until > you get to a few testsuite failures, but there seems no point in using > less than 2.3.1. > The timeline is whenever the mpfr maintainer gets to it. svn HEAD of gcc requires no less than mpfr 2.3.0, or top level configure fails. The current cygwin mpfr is 2.2.1. -- 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/