Re: Proposed CHOST change for the 64bit time_t transition
"Andreas K. Huettel" <[email protected]> Thu, 05 Sep 2024 19:03:35 +0200
| Newsgroups | dev.linux.lists.distributions |
|---|---|
| Organization | Gentoo Linux |
| Message-ID | <2015989.tdWV9SEqCh@noumea> |
--nextPart2314430.irdbgypaU6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; protected-headers="v1" From: "Andreas K. Huettel" <[email protected]> Subject: Re: Proposed CHOST change for the 64bit time_t transition Date: Thu, 05 Sep 2024 19:03:35 +0200 Message-ID: <2015989.tdWV9SEqCh@noumea> Organization: Gentoo Linux In-Reply-To: <[email protected]> MIME-Version: 1.0 > One possible improvement would be to append "t32" if you want 32-bit=20 > time_t, instead of appending "t64" for 64-bit time_t.=20 I hope you aren't earnestly proposing this worst of both worlds idea=20 (let's change CHOST for any system with no ABI change). > I felt the same way about the 64-bit off_t back in the 1990s. It was=20 > obvious to me even at the time that we would have been significantly=20 > better off making off_t 64-bit, while keeping 32-bit off_t in the ABI=20 > for backward compatibility; this is what NetBSD did with time_t in 2012.= =20 > Although I realize others felt differently, I never fully understood=20 > their concerns. >=20 > And here I am, three decades later, still having to make changes[1] to=20 > Autoconf's AC_SYS_LARGEFILE macro to continue to support that=20 > 30-year-old off_t mistake, and now with 64-bit time_t interacting with=20 > 64-off_t in non-orthogonal ways. Well, at least time64 implies largefile, so that will get sorted as side effect. =2D-=20 Andreas K. H=FCttel [email protected] Gentoo Linux developer=20 (council, comrel, toolchain, base-system, perl, libreoffice) https://wiki.gentoo.org/wiki/User:Dilfridge --nextPart2314430.irdbgypaU6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE/Rnm0xsZLuTcY+rT3CsWIV7VQSoFAmbZ5GcACgkQ3CsWIV7V QSqSaRAAt19Hnk1PviO+t1RYEEzKWVoRqhdH4CBh2zrxARQ68euzaxm7mTo++8FF wmhgWrIA1/YT+0udgCH9Kbo/jJvG1MDLhZ3kypTcQDHddy+zKANsvF4Ow55o9sg2 Y3GlrIK7bAw4jX93Uqi+NMoUSswyJCMopr/dmABwVCt5GPFwjyKS1GlhJGSxidOS APXQt/MEWGZR82R685a5xH5BBf1Wo+2qyRBWH9EX/AoVk2dP5JX2jfG4Aclmgxja BAactksAqaRJC4Yy0W/eNzafjtuzJXHAG0lwZmPQa9X1L3WvK8kMs3pkxIzBF5UR +GG+cRyVv7Z6T5+qcRhA5oqApGVXeNC9UI7wG8dwKomVUNFWqdP3gr1foHXjmKPr bMVDqB63nHBoxt1TbJx3JhD0G3lopRK89TdO1sGyR2svYkHb27Pvv2kajZZAv63R iXqK8J8fXAE2zGpgEOFdxh+woSOS4Rg2ohdl90cyKi7rGGn/m5mCDkroJ2BNop0s LVYK6mRpgxwH/9wCMKeJbm/Dj5DfpegEGqtRYLY0lWQ99nubGvTN7y2+Jq8G92zw QXOhs011Uc1glf8uR3WpWSJAF5SfuA1DJFcWxLThE+sY7aSfP9CC5iAIknBa+5u9 BAUvBji8ys+c4sN3MpkDM0rp7hKl3b2PnVQ9wQ7KSwFnCQccYUg= =4RQy -----END PGP SIGNATURE----- --nextPart2314430.irdbgypaU6--