Re: Proposed CHOST change for the 64bit time_t transition

--0l//PxkQOa9boaIv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 04, 2024 at 17:48:04 +0200, Andreas K. Huettel wrote:
> Dear all,=20
>=20
> in Gentoo Linux we want to change our CHOST triplets for 32-bit glibc sys=
tems that use 64-bit time_t, since
> this is technically an ABI change which breaks binary compatibility [1].
>=20
> We are thinking of adding a "t64" suffix to the ABI field, resulting in f=
or example i686-pc-linux-gnut64,
> armv7a-unknown-linux-gnueabihft64, ... [2]
>=20
> * So far my research indicates that in the GNU toolchain (gcc, glibc, bin=
utils) anything behind -gnu is=20
>   ignored (as ABI version, which this effectively is too). Is this correc=
t or do you foresee problems here?
>   I've had a small chroot rebuild itself (the Gentoo @system set) with i6=
86-pc-linux-gnut64 and only had to
>   add a minor patch to ncurses [3]; everything else worked fine.
>=20

=2E..

> [3] https://bpa.st/HV6BS

FYI, this paste expires in 1 week. Here's the contents:

diff '--color=3Dauto' -ruN ncurses-6.4.orig/aclocal.m4 ncurses-6.4/aclocal.=
m4
--- ncurses-6.4.orig/aclocal.m4	2024-08-29 20:47:34.978057133 +0000
+++ ncurses-6.4/aclocal.m4	2024-08-29 20:48:57.809473044 +0000
@@ -10139,7 +10139,7 @@
 	cf_xopen_source=3D"-D_SGI_SOURCE"
 	cf_XOPEN_SOURCE=3D
 	;;
-(linux*gnu|linux*gnuabi64|linux*gnuabin32|linux*gnueabi|linux*gnueabihf|li=
nux*gnux32|uclinux*|gnu*|mint*|k*bsd*-gnu|cygwin|msys|mingw*|linux*uclibc)
+(linux*gnu*|uclinux*|gnu*|mint*|k*bsd*-gnu|cygwin|msys|mingw*|linux*uclibc)
 	CF_GNU_SOURCE($cf_XOPEN_SOURCE)
 	;;
 (minix*)

--0l//PxkQOa9boaIv
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQQfOU+JeXjo4uxN6vCp8he9GGIfEQUCZtj8IgAKCRCp8he9GGIf
Ef64AQDRWB3iutTanlfsHGLAbzDqCRo0QhDIAYHXyhtajll7YQEA07Ox/xR/RILT
mphlh5QIfnqRrE95HnV0tqSB97k0Fw0=
=Zh2M
-----END PGP SIGNATURE-----

--0l//PxkQOa9boaIv--