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 203273858425 for ; Sat, 12 Nov 2022 04:01:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 203273858425 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=_204B08E4-964C-40F7-BB27-4B83F41DB1C0"; 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: <288fe53e-c58c-c179-0ead-65b4df321537@cs.ucla.edu> Date: Sat, 12 Nov 2022 04:00:48 +0000 Cc: Zack Weinberg , Michael Orlitzky , Autoconf Development , c-std-porting@lists.linux.dev, GCC Development Message-Id: <9356B8F9-7DD9-439C-AD36-67FC24029FB0@gentoo.org> References: <24ed5604-305a-4343-a1b6-a789e4723849@app.fastmail.com> <1d3109aa-c810-4c20-bcb9-d9d059d530a6@app.fastmail.com> <66E0EB7B-1296-4442-B3A7-6811FD68290D@gentoo.org> <288fe53e-c58c-c179-0ead-65b4df321537@cs.ucla.edu> To: Paul Eggert X-Mailer: Apple Mail (2.3731.200.110.1.12) X-Spam-Status: No, score=-4.2 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=_204B08E4-964C-40F7-BB27-4B83F41DB1C0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 12 Nov 2022, at 00:53, Paul Eggert wrote: >=20 > On 2022-11-11 15:25, Sam James wrote: >> That's not a judgement on whether the changes will ultimately remain = in autoconf, I'm just >> hesitant to allow a discussion I've kicked off to derail something = that we were planning >> on doing anyway. >> What do you think? >=20 > I'm hesitant to do that partly because the changes to _TIME_BITS are = already released in multiple packages and need to be dealt with, = regardless of whether they're backed out of Autoconf. This is because = they've been in Gnulib since July and several packages based on these = Gnulib changes have been released since then. Current Gnulib assumes = these changes will appear in the next Autoconf release; if that's not = true, we'll need to upgrade Gnulib and in the meantime the other = packages released since July would still have the changes whatever we do = with Gnulib and/or Autoconf. >=20 > Since distros need to deal with the issue anyway, regardless of what = Autoconf and/or Gnulib does, I don't see why backing the changes out of = Autoconf will help all that much. >=20 > It should pretty easy for a distro to say "hold on, I don't want = 64-bit time_t yet" without changing either Autoconf or Gnulib so if you = want to go that route please feel free to do so. The fact it's already shipped in gnulib & that the "real problem" is in = glibc IMO means that I don't feel strongly about reverting it. You're right that distros have the toggle so as long as we mention this = prominently enough in NEWS, I don't have a strong objection to master being released as-is. --Apple-Mail=_204B08E4-964C-40F7-BB27-4B83F41DB1C0 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+RkAUCY28acV8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MAAKCRBzhAn1IN+R kAnAAP9aOmGHuRwUdWEUKZZ66+tuWNfmcjPBsfInswIV5tkVoAD+M83K8OA2+y6k RxN6Sg2lLk5rcyH7B3jl76T4PaYkfwM= =/zby -----END PGP SIGNATURE----- --Apple-Mail=_204B08E4-964C-40F7-BB27-4B83F41DB1C0--