From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id F343B3857374 for ; Fri, 20 May 2022 12:43:11 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org F343B3857374 Received: from linux-libre.fsfla.org ([209.51.188.54]:53820 helo=free.home) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ns1yH-0004Ci-CZ; Fri, 20 May 2022 08:43:09 -0400 Received: from livre (livre.home [172.31.160.2]) by free.home (8.15.2/8.15.2) with ESMTPS id 24KCguFo416446 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 20 May 2022 09:42:56 -0300 From: Alexandre Oliva To: Martin =?utf-8?Q?Li=C5=A1ka?= Cc: Andreas Schwab , gcc-patches@gcc.gnu.org, Joseph Myers Subject: Re: [PATCH] configure: add --disable-fix-includes Organization: Free thinker, not speaking for the GNU Project References: <2e2c7061-3f3f-fde4-6e8c-d2118820a5b6@suse.cz> <87pmkkutdz.fsf@igel.home> Errors-To: aoliva@lxoliva.fsfla.org Date: Fri, 20 May 2022 09:42:55 -0300 In-Reply-To: ("Martin \=\?utf-8\?Q\?Li\=C5\=A1ka\=22's\?\= message of "Wed, 11 May 2022 16:50:54 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 2.84 X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2022 12:43:15 -0000 On May 11, 2022, Martin Li=C5=A1ka wrote: > Ready to be installed? Hmm... I don't like that --disable-fixincludes would still configure, build and even install fixincludes. This would be surprising, given that the semantics of disabling a component is to not even configure it. How about leaving the top-level alone, and changing gcc/configure.ac to clear STMP_FIXINC when --disable-fixincludes is given? --=20 Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/ Free Software Activist GNU Toolchain Engineer Disinformation flourishes because many people care deeply about injustice but very few check the facts. Ask me about