public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Denis Excoffier <cygwin@Denis-Excoffier.org>
To: cygwin@cygwin.com
Subject: Re: gcc-4.7.0-RC-20120302 fails to build for i686-pc-cygwin
Date: Thu, 22 Mar 2012 07:25:00 -0000	[thread overview]
Message-ID: <20120322072533.GA2948@qp9482> (raw)
In-Reply-To: <4F5764E3.8090004@gmail.com>

On Wed, Mar 07, 2012 at 01:38:43PM +0000, Dave Korn wrote:
>> 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<process.h>  and the file actually lives in
>> >>> <cygwin/process.h>  (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.
>> 

Perhaps we could nevertheless find a means to move <process.h>
into <cygwin/process.h>, while not breaking GCC compilation during
the mean time? A patch to GCC-4.8 to search first for <cygwin/process.h>
and <process.h> if not found? And, for Cygwin,
cp -p cygwin/process.h process.h? SHTDI.

Regards,

Denis Excoffier.

--
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

  reply	other threads:[~2012-03-22  7:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 12:54 Ryan Johnson
2012-03-07 13:06 ` marco atzeri
2012-03-07 13:08 ` Corinna Vinschen
2012-03-07 13:34   ` Ryan Johnson
2012-03-07 13:39     ` Dave Korn
2012-03-22  7:25       ` Denis Excoffier [this message]
2012-03-22 13:32         ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120322072533.GA2948@qp9482 \
    --to=cygwin@denis-excoffier.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).