From: Richard Henderson <rth@redhat.com>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: NightStrike <nightstrike@gmail.com>,
Ozkan Sezer <sezeroz@gmail.com>,
Richard Guenther <richard.guenther@gmail.com>,
Danny Smith <dansmister@gmail.com>,
Dave Korn <dave.korn.cygwin@googlemail.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [patch win32]: fix for PR target/41943
Date: Thu, 22 Jul 2010 21:57:00 -0000 [thread overview]
Message-ID: <4C48BECA.5080405@redhat.com> (raw)
In-Reply-To: <AANLkTinz0BCpGc3p-Fvdg7CGv_fPVnUnKkD-xFDfWYr3@mail.gmail.com>
On 07/22/2010 02:51 PM, Kai Tietz wrote:
> To the point that gcc intends that gcc's internal headers should be
> used by default. And so it would be wise to put even
> /usr/local/include behind at least fixinclude, as this would be
> strict.
> And secondly, that this patch to add #include_next should be the
> solution. Also it means that Danny has to think about a different
> place mingw.org hasto put the runtime headers into.
>
> Did I read you correct?
I believe all that is correct.
In order to make process on the second part above, it would seem
that your include_next patch is going to have to be backported to
whatever compiler version mingw.org is using.
That's a bit of release management I'm not sure how best to coordinate.
r~
next prev parent reply other threads:[~2010-07-22 21:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 13:27 Ozkan Sezer
2010-07-22 16:00 ` Richard Henderson
2010-07-22 16:02 ` Ozkan Sezer
2010-07-22 16:05 ` Richard Henderson
2010-07-22 16:08 ` Ozkan Sezer
2010-07-22 16:50 ` Kai Tietz
2010-07-22 19:36 ` NightStrike
2010-07-22 20:06 ` Richard Henderson
2010-07-22 20:25 ` NightStrike
2010-07-22 20:33 ` Richard Henderson
2010-07-22 20:36 ` Kai Tietz
2010-07-22 21:11 ` Richard Henderson
2010-07-22 21:20 ` Kai Tietz
2010-07-22 21:33 ` Richard Henderson
2010-07-22 21:39 ` Kai Tietz
2010-07-22 21:42 ` Richard Henderson
2010-07-22 21:51 ` Kai Tietz
2010-07-22 21:57 ` Richard Henderson [this message]
2010-07-23 17:55 ` Kai Tietz
2010-07-23 18:13 ` Richard Henderson
2010-07-23 18:33 ` Kai Tietz
2010-07-23 9:14 ` Richard Guenther
2010-07-27 15:19 ` Joseph S. Myers
2010-07-28 9:49 ` Kai Tietz
-- strict thread matches above, loose matches on Subject: below --
2010-07-22 8:13 Ozkan Sezer
2010-07-21 19:38 Kai Tietz
2010-07-21 20:41 ` Richard Henderson
2010-07-21 21:34 ` Kai Tietz
2010-07-21 22:05 ` Danny Smith
2010-07-22 7:46 ` Kai Tietz
2010-07-22 11:38 ` Danny Smith
2010-07-22 11:42 ` Kai Tietz
2010-07-22 11:49 ` Richard Guenther
2010-07-22 11:56 ` Kai Tietz
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=4C48BECA.5080405@redhat.com \
--to=rth@redhat.com \
--cc=dansmister@gmail.com \
--cc=dave.korn.cygwin@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ktietz70@googlemail.com \
--cc=nightstrike@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=sezeroz@gmail.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).