summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2007-05-25 23:23:18 +0000
committerNick Mathewson <nickm@torproject.org>2007-05-25 23:23:18 +0000
commit20773596d3710a878a353082483090f6412364b4 (patch)
treeda1076b1a778a5c492dc5f891c6b7bd86e38630b
parent9204034cf0f3a5ba8d25449c2cb54eb46efbca5b (diff)
downloadtor-20773596d3710a878a353082483090f6412364b4.tar.gz
tor-20773596d3710a878a353082483090f6412364b4.zip
r12981@catbus: nickm | 2007-05-25 19:23:12 -0400
Always default to "No threads" on net/openbsd in 0.1.2, even with eventdns, since apparently they have had no real testing up to this point, and 0.1.2.x is supposed to be stable. svn:r10344
-rw-r--r--configure.in10
1 files changed, 9 insertions, 1 deletions
diff --git a/configure.in b/configure.in
index 166563c05b..e7c95feb25 100644
--- a/configure.in
+++ b/configure.in
@@ -51,7 +51,15 @@ if test x$enable_threads = x; then
AC_MSG_NOTICE([You are running OpenBSD or NetBSD; I am assuming that
getaddrinfo is not threadsafe here, so I will disable threads.])
enable_threads="no"
- fi ;;
+ else
+ # This was an inadvertant default up through 0.1.2.14; in 0.2.0.x,
+ # it's getting some testing, but for now, best leave threads off
+ # unless the user urns them on.
+ AC_MSG_NOTICE([You are running OpenBSD or NetBSD; Tor 0.1.2.x hasn't
+been tested with threads on these platforms, so I'm turning them off. You
+can enable threads by passing --enable-threads to the configure script.])
+ enable_threads="no"
+ fi ;;
*-*-solaris* )
# Don't try multithreading on solaris -- cpuworkers seem to lock.
AC_MSG_NOTICE([You are running Solaris; Sometimes threading makes