LONG_MAX is not the maximum value of 64-bit time_t on 32 bit systems (e.g. ARMv7)

[xypron]

The library makes the false assumption that time_t is equivalent to long. To avoid the year 2038 problem Linux distributions like Debian and Ubuntu have moved to using 64-bit time_t on 32-bit architectures like ARMv7.

Now we see test failures like:

FAIL tltest-timespec.c:169 -2147483648.999999999 cap- 2147483647.999999999 = 0.999999998 != -2147483648.999999999
FAIL tltest-timespec.c:170 2147483647.999999999 cap- -2147483648.999999999 = 0.999999998 != 2147483647.999999999

To resolve the issue tlog should check the width of time_t and define symbols for the minimum and maximum values of time_t accordingly.

[xypron]

Launchpad bug: https://bugs.launchpad.net/ubuntu/+source/tlog/+bug/2059028

[justin-stephenson]

Thank you for the report. Would you mind submitting a PR if you have a fix already ?