From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 116907 invoked by alias); 31 May 2019 15:19:06 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 116899 invoked by uid 89); 31 May 2019 15:19:06 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 spammy=HX-Languages-Length:957 X-HELO: mailrelay0.sft.mx Received: from blergh.sft.mx (HELO mailrelay0.sft.mx) (37.120.163.187) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 31 May 2019 15:19:05 +0000 Received: from jjserver.sft.mx (unknown [188.192.97.57]) (Authenticated sender: jjservermail@mailrelay0.sft.mx) by mailrelay0.sft.mx (Postfix) with ESMTPSA id 20B7C20F94; Fri, 31 May 2019 17:19:03 +0200 (CEST) Received: from [131.159.212.140] (w212-3w-v4.eduroam.dynamic.rbg.tum.de [131.159.212.140]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by jjserver.sft.mx (Postfix) with ESMTPSA id 06719A4030B; Fri, 31 May 2019 17:19:00 +0200 (CEST) Subject: Re: [PATCH] fixincludes breaks mingw64 build To: Jonathan Wakely Cc: gcc-patches@gcc.gnu.org, bkorb@gnu.org References: <3eb89802-0cfb-1888-00b6-357d76370894@sft.mx> <20190531143816.GA30354@redhat.com> From: Jonas Jelten Message-ID: <37e6c2cd-a59d-0f09-b502-b991387d406b@sft.mx> Date: Fri, 31 May 2019 15:35:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190531143816.GA30354@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-05/txt/msg02137.txt.bz2 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. """ -- JJ