From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) by sourceware.org (Postfix) with ESMTP id 589443858D35 for ; Fri, 11 Nov 2022 03:08:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 589443858D35 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gentoo.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gentoo.org Content-Type: multipart/signed; boundary="Apple-Mail=_BE6A0A05-F644-4622-ABC6-49E4B18CF046"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.200.110.1.12\)) Subject: Re: How can Autoconf help with the transition to stricter compilation defaults? From: Sam James In-Reply-To: Date: Fri, 11 Nov 2022 03:08:19 +0000 Cc: autoconf@gnu.org, c-std-porting@lists.linux.dev, GCC Development , GCC Development Message-Id: References: <24ed5604-305a-4343-a1b6-a789e4723849@app.fastmail.com> To: Michael Orlitzky , Zack Weinberg X-Mailer: Apple Mail (2.3731.200.110.1.12) X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --Apple-Mail=_BE6A0A05-F644-4622-ABC6-49E4B18CF046 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 10 Nov 2022, at 21:10, Michael Orlitzky = wrote: >=20 > On Thu, 2022-11-10 at 12:16 -0500, Zack Weinberg wrote: >>=20 >> Nobody has a whole lot of time to work on Autoconf at present, but I >> would like to ask, anyway, what Autoconf could potentially do to make >> this transition easier. >=20 > While everyone else is discussing big ideas, it would be helpful for = me > personally if autoconf just made a release with the latest bugfixes. >=20 > I report these compatibility issues upstream, and it's awkward to have > to tell the maintainers that they must cherry-pick a git commit, > rebuild autoconf, and then autoreconf their project before they can > even even think about exporting CFLAGS=3D"-Werror=3D..." to build-test > their project. >=20 >=20 Before I dive into the rest of this thread: yes, this is one of my main thoughts on the matter. Autoconf has a huge network effect problem and letting the existing fixes start to propagate would be most helpful. Like it or not (and I don't like it), various software tries to jam in -Werror (and sometimes -pedantic-errors, see rsync!) to their configure scripts which means even prototype issues end up causing problems. Note that in autoconf git, we've also got = https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=3Df6657256a37da4= 4c987c04bf9cd75575dfca3b60 which is going to affect time_t efforts too, but that's for another thread on libc-alpha at some point when I want to bring up some issues. --Apple-Mail=_BE6A0A05-F644-4622-ABC6-49E4B18CF046 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iNUEARYKAH0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCY228pF8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MAAKCRBzhAn1IN+R kEhcAQCe38XkiiQng+O3YcXs0DelkNRZEt9aL8GLgbfW56TcdgD8CY65TcoTwsr1 PvXyw2YGCTpQSiwbrNGB1mhHPQRMeQc= =vRhF -----END PGP SIGNATURE----- --Apple-Mail=_BE6A0A05-F644-4622-ABC6-49E4B18CF046--