tor/changes/warn-unsigned-time_t

  o Minor bugfixes (portability):
    - On the chance that somebody manages to build Tor on a
      platform where time_t is unsigned, correct the way that
      microdesc_add_to_cache handles negative time arguments. Fix for
      bug 8042; bugfix on 0.2.3.1-alpha.

  o Build improvements:
    - Warn if building on a platform with an unsigned time_t: there
      are too many places where Tor currently assumes that time_t can
      hold negative values. We'd like to fix them all, but probably
      some will remain.
Fix a bug in microdescs_add_to_cache when listed_at == -1 This bug affects hosts where time_t is unsigned, which AFAICT does not include anything we currently support. (It _does_ include OpenVMS, about a month of BSD4.2's history[1], and a lot of the 1970s.) There are probably more bugs when time_t is unsigned. This one was [1] http://mail-index.netbsd.org/tech-userlevel/1998/06/04/0000.html 2013-03-11 21:20:20 +01:00			`o Minor bugfixes (portability):`
			`- On the chance that somebody manages to build Tor on a`
			`platform where time_t is unsigned, correct the way that`
			`microdesc_add_to_cache handles negative time arguments. Fix for`
			`bug 8042; bugfix on 0.2.3.1-alpha.`

Warn at configure time when time_t is unsigned Inspired by #8042. As far as I know, OpenVMS is the only place you're likely to hit an unsigned time_t these days, and Tor's VMS support is... lacking. Still worth letting people know about it, though. 2013-03-11 20:33:44 +01:00			`o Build improvements:`
			`- Warn if building on a platform with an unsigned time_t: there`
			`are too many places where Tor currently assumes that time_t can`
			`hold negative values. We'd like to fix them all, but probably`
			`some will remain.`