diff options
| author | Nick Mathewson <nickm@torproject.org> | 2013-03-11 15:33:44 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2013-03-11 15:33:44 -0400 |
| commit | 2f98bf5c9fac4dfd1bb07564ce08b13d1e330252 (patch) | |
| tree | cbd37edff429666bbb4b05ff9780c4ec7d66f2ea /changes | |
| parent | ef4db3169344567f30fb72e3e9a66154b976d889 (diff) | |
| download | tor-2f98bf5c9fac4dfd1bb07564ce08b13d1e330252.tar tor-2f98bf5c9fac4dfd1bb07564ce08b13d1e330252.tar.gz | |
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.
Diffstat (limited to 'changes')
| -rw-r--r-- | changes/warn-unsigned-time_t | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/changes/warn-unsigned-time_t b/changes/warn-unsigned-time_t new file mode 100644 index 000000000..5f0c36d09 --- /dev/null +++ b/changes/warn-unsigned-time_t @@ -0,0 +1,5 @@ + 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. |