From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6307 invoked by alias); 31 May 2019 14:38:23 -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 6299 invoked by uid 89); 31 May 2019 14:38:23 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.1 spammy=snip, HX-Languages-Length:643 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 31 May 2019 14:38:22 +0000 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id BE62BC0AD292; Fri, 31 May 2019 14:38:20 +0000 (UTC) Received: from localhost (unknown [10.33.36.135]) by smtp.corp.redhat.com (Postfix) with ESMTP id 524A32FC53; Fri, 31 May 2019 14:38:17 +0000 (UTC) Date: Fri, 31 May 2019 14:51:00 -0000 From: Jonathan Wakely To: Jonas Jelten Cc: gcc-patches@gcc.gnu.org, bkorb@gnu.org Subject: Re: [PATCH] fixincludes breaks mingw64 build Message-ID: <20190531143816.GA30354@redhat.com> References: <3eb89802-0cfb-1888-00b6-357d76370894@sft.mx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <3eb89802-0cfb-1888-00b6-357d76370894@sft.mx> X-Clacks-Overhead: GNU Terry Pratchett User-Agent: Mutt/1.11.3 (2019-02-01) X-SW-Source: 2019-05/txt/msg02132.txt.bz2 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.