Re: Proposed CHOST change for the 64bit time_t transition

[Oskari Pirhonen <xxc3ncoredxx@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]

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

...

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

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

diff '--color=auto' -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="-D_SGI_SOURCE"
 	cf_XOPEN_SOURCE=
 	;;
-(linux*gnu|linux*gnuabi64|linux*gnuabin32|linux*gnueabi|linux*gnueabihf|linux*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*)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]