From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by sourceware.org (Postfix) with ESMTPS id CF707384F033 for ; Sat, 12 Nov 2022 16:13:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org CF707384F033 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=owlfolio.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=owlfolio.org Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 0CFF65C0093; Sat, 12 Nov 2022 11:13:57 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sat, 12 Nov 2022 11:13:57 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=owlfolio.org; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; t=1668269637; x=1668356037; bh=43PP66jo0U JcetaVnTzAfosmOnJzRFm0wU59sCQpdQU=; b=iKXDBtQpkJ7GNsR6RSLz4hsZKl UtZgQMYvcnBoXtqFIa08L0iFNPDlQ1ZRbIWMD2CYhUmT50IuL896KCraWwKS/Wf5 MFyrkiX0Keu679FXm78ohCv0P1nLkV0MzC0GiP2Z36vnboizayHSVWecpGzQckAc qHbhf6AUJ+6Xt7kgx+nqrBN95bOMKFIZSRT9STH+A3fYLy2sqUc/AnX/eZtWs3/6 hMH+77rzEw837q6qjfkwJBq00OetKBd4qIPxeBCsCgJUTcYqa1mVLu/vLNlj7REE oZWBig2yKkvN7hWglHtCV1bBj0YKawfRY3krZdpymkY4L3gdnyeY1CIq5IOA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1668269637; x=1668356037; bh=43PP66jo0UJcetaVnTzAfosmOnJz RFm0wU59sCQpdQU=; b=CW599xlkKEQdjUKtUCqjqd1V2LtT8legIbtD12tmfG1h Ah9dIvNdRXzmwLlOtEG0MQ9cjwmqNqPGZ1KPQSUEH9S9rWXCuJR/u3iEDbnbyW3W I74ARBQw0dEYYGx/YDwgL4uW2v+5T45V18pWkoHV2qN1pVEfD4423FZsxhmo6Ztc PmM7ek59VhSQRX0HdBD9UHZhdU5ChH59VwENw0uk9BCYYz7pqSFPwljlRSfeWxCx TiuNtDlYH5btgcTmIjTHGtlFXSnW0gmwfnJFhPdMEj+np7CveOmJDGL58AnGNU1S QUkjONhbVgT7QofAw/lwONdGoFcCzNPOG+ZKO350Vw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedrfeekgdekiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufhfffgjkfgfgggtsehttdertddtredtnecuhfhrohhmpegkrggtkhcu hggvihhnsggvrhhguceoiigrtghksehofihlfhholhhiohdrohhrgheqnecuggftrfgrth htvghrnhepvdfgvdeiledvvdefkeelgfdtffejudfgfefffeeuueevuedthfeigfetuddu heeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepii grtghksehofihlfhholhhiohdrohhrgh X-ME-Proxy: Feedback-ID: i876146a2:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 12 Nov 2022 11:13:56 -0500 (EST) From: Zack Weinberg To: Wookey Cc: Florian Weimer , , c-std-porting@lists.linux.dev, autoconf@gnu.org, cfe-commits@lists.llvm.org, Frederic Berat Subject: Re: How can Autoconf help with the transition to stricter compilation defaults? References: <24ed5604-305a-4343-a1b6-a789e4723849@app.fastmail.com> <87v8nmsmwt.fsf@oldenburg.str.redhat.com> <20221112155952.GM27919@mail.wookware.org> Date: Sat, 12 Nov 2022 11:12:38 -0500 In-Reply-To: <20221112155952.GM27919@mail.wookware.org> (wookey@wookware.org's message of "Sat, 12 Nov 2022 15:59:52 +0000") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,JMQ_SPF_NEUTRAL,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Wookey writes: > On 2022-11-10 19:08 +0100, Florian Weimer wrote: >> based on a limited attempt to get this fixed about three years >> ago, I expect that many of the problematic packages have not had their >> configure scripts regenerated using autoconf for a decade or more. This >> means that as an autoconf maintainer, you unfortunately won't be able to >> help us much. > > We changed the default in debian to re-autoconf on build a few years > ago precisely so that changes in the tools (particularly new arch > support) were picked up even by code that was not being re-released or > released without autofoo updates. This has worked remarkably well. > > So changes in the tools will get used, at least in that context, which > includes a fairly hefty pile of crufty old code. I have no feeling for > how many packages are actually affected by this. Is there a quick way to test? In the run-up to Autoconf 2.70 I got Lucas to do a Debian archive rebuild and mass bug filing, so, look through Debian packages for patches being carried for configure.ac and/or bundled .m4 files? zw