X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_DF X-Spam-Check-By: sourceware.org Subject: Re: Still on target for imminent 1.7.8 release? [was Re: Enable dfp routines in compiler support lib] From: "Yaakov (Cygwin/X)" To: cygwin In-Reply-To: <4D4023F5.8030207@cwilson.fastmail.fm> References: <4D3EF76F.7090408@users.sourceforge.net> <4D3F7C6F.4060600@gmail.com> <4D3F76E2.80207@users.sourceforge.net> <4D3F9AC6.3040605@gmail.com> <20110126103331.GK28470@calimero.vinschen.de> <4D4023F5.8030207@cwilson.fastmail.fm> Content-Type: text/plain; charset="UTF-8" Date: Wed, 26 Jan 2011 17:00:31 -0600 Message-ID: <1296082831.2856.1.camel@YAAKOV04> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Wed, 2011-01-26 at 08:39 -0500, Charles Wilson wrote: > Dave, I'd recommend allowing that patch to gcc, which requires fenv.h, > to be committed, given that the 4.6 window is closing soon... > > ...and it'll force the two people who might actually try to compile > bleeding edge gcc 4.6 to go ahead and install -- and test -- the cygwin > dev snaps. +1 I see no reason why cutting edge GCC can't require a cutting edge Cygwin. Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple