From: Jonathan Wakely <jwakely@redhat.com>
To: Jonas Jelten <jj@sft.mx>
Cc: gcc-patches@gcc.gnu.org, bkorb@gnu.org
Subject: Re: [PATCH] fixincludes breaks mingw64 build
Date: Fri, 31 May 2019 19:48:00 -0000 [thread overview]
Message-ID: <20190531191556.GA2599@redhat.com> (raw)
In-Reply-To: <37e6c2cd-a59d-0f09-b502-b991387d406b@sft.mx>
On 31/05/19 17:18 +0200, Jonas Jelten wrote:
>On 31/05/2019 16.38, Jonathan Wakely wrote:
>> On 31/05/19 15:35 +0200, Jonas Jelten wrote:
>>> Hi!
>>>
>>> I'm trying to build the x86_64-w64-mingw64 crosscompiler on gentoo.
>>> It breaks because a fixincludes-fix is applied at a place where it should not be applied.
>>>
>>> This broke the cross-gcc build for gcc-8.3.0 and 9.1.0 with error messages that made it tricky to figure out what was
>>> really going on.
>>
>> [snip]
>>
>> N.B. The gcc-bugs mailing list is for automated email from Bugzilla,
>> not for reporting bugs. Sending the patch to gcc-patches (and CCing a
>> relevant maintainer) is correct, but there's no need (and no point) to
>> also send it to gcc-bugs.
>>
>>
>
>
>Alright, thanks for the hint. I was just following the instructions in gcc-9.1.0/fixincludes/README:
>
>"""
>Please also send relevant information to gcc-bugs@gcc.gnu.org, gcc-patches@gcc.gnu.org and,
>please, to me: bkorb@gnu.org.
>"""
Oh, indeed!
Bruce, should that suggest submitting something to Bugzilla instead?
Mails sent directly to gcc-bugs tend to get lost among all the
automated email from Bugzilla.
next prev parent reply other threads:[~2019-05-31 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 13:59 Jonas Jelten
2019-05-31 14:51 ` Jonathan Wakely
2019-05-31 15:35 ` Jonas Jelten
2019-05-31 19:48 ` Jonathan Wakely [this message]
2019-06-11 20:38 ` Bruce Korb
2019-08-12 22:09 ` Gerald Pfeifer
2019-06-11 20:32 ` Bruce Korb
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=20190531191556.GA2599@redhat.com \
--to=jwakely@redhat.com \
--cc=bkorb@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jj@sft.mx \
/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).