From 5f7df92571ec5a2d1eddb257e22f5489acc4fc83 Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Fri, 29 Jan 2016 09:18:59 -0500 Subject: Remove support for unsigned time_t We've never actually tested this support, and we should probably assume it's broken. To the best of my knowledge, only OpenVMS has this, and even on OpenVMS it's a compile-time option to disable it. And I don't think we build on openvms anyway. (Everybody else seems to be working around the 2038 problem by using a 64-bit time_t, which won't expire for roughly 292 billion years.) Closes ticket 18184. --- changes/bug18184 | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 changes/bug18184 (limited to 'changes') diff --git a/changes/bug18184 b/changes/bug18184 new file mode 100644 index 0000000000..af493df75f --- /dev/null +++ b/changes/bug18184 @@ -0,0 +1,5 @@ + o Removed platform support: + - Tor no longer attempts to support platforms where the "time_t" type + is unsigned. (To the best of our knowledge, only OpenVMS does this, + and Tor has never actually built on OpenVMS.) Closes ticket 18184. + -- cgit v1.2.3-54-g00ecf