[tor-commits] [tor/master] Bufferevents now requires Libevent 2.0.13-stable.

[nickm at torproject.org]

commit 893291936643514b49ece77d5aecab20e52e2200
Author: Nick Mathewson <nickm at torproject.org>
Date:   Wed Aug 17 12:53:50 2011 -0400

    Bufferevents now requires Libevent 2.0.13-stable.
    
    (Earlier Libevent versions have bufferevent bugs that affect us, and
    are missing some APIs that it would be handy to use.)
---
 changes/require-le-2.0.13 |    7 +++++++
 configure.in              |    4 ++--
 2 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/changes/require-le-2.0.13 b/changes/require-le-2.0.13
new file mode 100644
index 0000000..0b9b2f9
--- /dev/null
+++ b/changes/require-le-2.0.13
@@ -0,0 +1,7 @@
+  o Build changes:
+    - Building Tor with bufferevent support now requires Libevent
+      2.0.13-stable or later. Previous versions of Libevent had bugs
+      in SSL-related bufferevents and related issues that would make
+      Tor work badly with bufferevents. Requiring 2.0.13-stable also
+      means that Tor with bufferevents can take advantage of Libevent
+      APIs introduced after 2.0.8-rc.
diff --git a/configure.in b/configure.in
index 6437183..4a89df6 100644
--- a/configure.in
+++ b/configure.in
@@ -438,7 +438,7 @@ int x = 1;
       AC_MSG_CHECKING([whether Libevent is new enough for bufferevents])
       AC_COMPILE_IFELSE([AC_LANG_SOURCE([
 #include <event2/event.h>
-#if !defined(LIBEVENT_VERSION_NUMBER) || LIBEVENT_VERSION_NUMBER < 0x02000800
+#if !defined(LIBEVENT_VERSION_NUMBER) || LIBEVENT_VERSION_NUMBER < 0x02000d00
 #error
 int x = y(zz);
 #else
@@ -446,7 +446,7 @@ int x = 1;
 #endif
    ])], [ AC_MSG_RESULT([yes]) ],
       [ AC_MSG_RESULT([no])
-        AC_MSG_ERROR([Libevent does not seem new enough to support bufferevents.  We require 2.0.8-rc or later]) ] )
+        AC_MSG_ERROR([Libevent does not seem new enough to support bufferevents.  We require 2.0.13-stable or later]) ] )
     fi
   fi
 fi