Subject: gzip-1.8.41 test results: timestamp

From: Bruno Haible <[email-masked]>
Date: Sun, 12 Nov 2017 00:36:29 +0100

Hi,

Here are test results of the today's gzip git + newest gnulib (= nearly
the same as Jim's gzip-1.8.40). I tested only 32-bit platforms.

1) On
Linux/i386 (on a bi-arch system):
Linux/hppa (on a Linux/x86_64 system):
Linux/m68k (on a Linux/x86_64 system):
Linux/arm (on a bi-arch system):
Linux/powerpc (on a bi-arch system):
Linux/s390 (on a bi-arch system):
AIX/powerpc (on a bi-arch system):

- By default:
configure: error: This package requires a 64-bit 'time_t' type, which your system appears to support. You might try configuring with 'CPPFLAGS="-m64" LDFLAGS="-m64"'. To build with a 32-bit time_t anyway (not recommended), configure with 'TIME_T_32_BIT_OK=yes'.
- With TIME_T_32_BIT_OK=yes:
FAIL: timestamp

2) On
Linux/x86_64-x32 (on a bi-arch system):
Linux/mips o32:
Linux/mips o32 (on a bi-arch system):
Linux/mips n32 (on a bi-arch system):
Linux/arm:
Hurd/i386:
NetBSD/i386:
Solaris 10/i386 (on a bi-arch system):
Solaris 10/sparc (on a bi-arch system):
Mac OS X/i386 (on a bi-arch system):
Mac OS X/powerpc (on an x86_64 system):

All tests pass.

3)
Linux/sparc (on a bi-arch system):

On some machines, like 1). On other machines, like 2).

4)
FreeBSD/i386:
Haiku/i386:
HP-UX/hppa:
HP-UX/ia64:

The timestamp test passes, but some other tests fail (see separate mail).

5)
OpenBSD/i386:
NetBSD/sparc:
IRIX n32:
FAIL: timestamp

Find attached the test-suite.log of each platform.

Bruno