X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Message-ID: <4F5764E3.8090004@gmail.com> Date: Wed, 07 Mar 2012 13:38:43 +0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: gcc-4.7.0-RC-20120302 fails to build for i686-pc-cygwin References: <4F575A90 DOT 8060201 AT cs DOT utoronto DOT ca> <20120307130723 DOT GB14210 AT calimero DOT vinschen DOT de> <4F5763D9 DOT 8030602 AT cs DOT utoronto DOT ca> In-Reply-To: <4F5763D9.8030602@cs.utoronto.ca> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 On 07/03/2012 13:34, Ryan Johnson wrote: > On 07/03/2012 8:07 AM, Corinna Vinschen wrote: >> On Mar 7 07:54, Ryan Johnson wrote: >>> Hi all, >>> >>> I tried to bootstrap the gcc-4.7 RC and it fails because it expects >>> to find and the file actually lives in >>> (see >>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52513). >>> >>> I'm asking here because the gcc devs thought this would mean 4.6 is >>> broken as well, but I have 4.6.2 running. Did process.h perhaps move >>> between 1.7.10 and 1.7.11? I guess configure must be using linker >>> rather than preprocessor tests for presence of spawnve, because it >>> thinks (correctly) that the function exists. >> See http://cygwin.com/ml/cygwin-announce/2012-02/msg00041.html >> We moved it back. If you have it in cygwin/process.h, you didn't >> update from 1.7.10 to 1.7.11. > Ah, I do remember that, now that you mention, but I was running a 1.7.11 > snapshot and forgot to upgrade... > > Thanks for the quick reply, > Ryan Thanks for spotting that Ryan. FTR, I figure it's not worth delaying the GCC release to add a fix to support .10, since there were other significant problems with it, and anyone who has it should be moving to .11 anyway. cheers, DaveK -- 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