On 2026-09-01 19:29, Collin Funk wrote:
Bruno Haible via "GNU gzip discussion and bug reports."
<[email protected]> writes:
Building it on bi-arch machines in 32-bit mode, the 'timestamp' test
may fail.
Find attached the logs of the builds on
- Linux (Debian 8)/s390x, CC="gcc -m31",
- Solaris 11.4/x86_64, CC="gcc -m32".
In the Linux (Debian 8) case, gzip prints a diagnostic
gzip: in: warning: file timestamp out of range for gzip format
In the Solaris 11.4 case, gzip prints a diagnostic
gzip: in: Value too large for defined data type
On Solaris calling fstat on the file fails with EOVERFLOW there.
Yes, I'm inclined to not go to much work here. Debian 8 is no longer supported,
and people using Solaris's or AIX's doddering 32-bit time_t configurations
should already know their systems won't work past 2038.
If someone wants to fancy up the test cases so that they skip these tests on
platforms that build gzip with 32-bit time_t even though 'touch' is 64-bit
time_t, that would be fine; but I'd rather it not be me.
Since we're close to a release let's do nothing for now. After the release we can change bootstrap.conf's
"year2038" to "year2038-recommended", so that old-fashioned configurers need to go to
some extra work to say "I want my programs to die a decade from now."
