Re: mktime.m4 - working mktime fails if TIME_T_IS_SIGNED us undefined.

On 09/22/2017 02:42 AM, Bruno Haible wrote: When we make changes to time_t related code, how to verify that it works with an unsigned time_t type? The way I do it in tzdb is to replace the system time_t and its related low-level

Re: mktime.m4 - working mktime fails if TIME_T_IS_SIGNED us undefined.

John E. Malmberg wrote: > The TIME_T_IS_SIGNED macro not defined if time_t is unsigned. > > This causes the test for working mtime to fail to compile on such > systems such as OpenVMS. Given that the bug was introduced on 2016-05-01, and that a web search for "checking whether time_t is signed..

Re: mktime.m4 - working mktime fails if TIME_T_IS_SIGNED us undefined.

Thanks for the heads-up. I installed the attached. It's not surprising that OpenVMS mktime fails the test. >From afc5fb6e9cb7a64609a7d18c260ed49aa98431a1 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Thu, 21 Sep 2017 21:39:59 -0700 Subject: [PATCH] mktime: port to OpenVMS Problem reported by

mktime.m4 - working mktime fails if TIME_T_IS_SIGNED us undefined.

The TIME_T_IS_SIGNED macro not defined if time_t is unsigned. This causes the test for working mtime to fail to compile on such systems such as OpenVMS. configure:33308: cc -o conftest -g conftest.c >&5 time_t_max = (! TIME_T_IS_SIGNED ..^ %CC-E-UNDECLARED, In this statem