From bd7037fdd108729999cfb32a1304abd0eec1d1ad Mon Sep 17 00:00:00 2001 From: Steve Bennett Date: Thu, 5 Mar 2020 09:08:34 +1000 Subject: build: Check for 32-bit time_t at configure time To warn of Y2038 problems, and suggest use of -D__MINGW_USE_VC2005_COMPAT on mingw32. Do this instead of the previous runtime test. Add -D__MINGW_USE_VC2005_COMPAT to the appveyor build. Fixes msteveb/jimtcl#145 Signed-off-by: Steve Bennett --- tests/clock.test | 5 ----- 1 file changed, 5 deletions(-) (limited to 'tests') diff --git a/tests/clock.test b/tests/clock.test index 3e9aec3..4e32df4 100644 --- a/tests/clock.test +++ b/tests/clock.test @@ -51,9 +51,4 @@ test clock-4.1 {clock scan tests} clockscan { clock scan {Sun Nov 04 03:02:46 AM 1990} -format {%a %b %d %I:%M:%S %p %Y} -gmt true } 657687766 -# This will fail on systems that are not Y2038 compliant -test clock-5.1 {Year 2038 compliance} { - clock format 2200000000 -format %Y-%m-%dT%H:%M:%S -gmt true -} 2039-09-18T23:06:40 - testreport -- cgit v1.1