X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-YMail-OSG: yUCe3jMVM1mNMViZzmavkJ6AejX1Ib967Sy_gPCoLvu2fFcaps0bm2NiON40A5ULPuVhdRtukA-- X-Yahoo-Newman-Property: ymail-3 Message-ID: <47DF532B.7060701@sbcglobal.net> Date: Mon, 17 Mar 2008 22:29:15 -0700 From: Tim Prince Reply-To: tprince AT computer DOT org User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: gmp/mpfr status References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 NightStrike wrote: > Is there an approximate timeline for when the gmp and mpfr packages > will be upgraded to the minimum required for compiling gcc? Really, I > guess it's just mpfr that has to be upgraded to 2.3.0., but I think > mpfr 2.3.0 requires gmp 4.2.2. > 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. -- 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/