[or-cvs] r10344: Always default to "No threads" on net/openbsd in 0.1.2, even (tor/branches/tor-0_1_2-patches)

[nickm@xxxxxxxx]

Author: nickm
Date: 2007-05-25 19:23:18 -0400 (Fri, 25 May 2007)
New Revision: 10344

Modified:
   tor/branches/tor-0_1_2-patches/
   tor/branches/tor-0_1_2-patches/configure.in
Log:
 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.



Property changes on: tor/branches/tor-0_1_2-patches
___________________________________________________________________
 svk:merge ticket from /tor/012 [r12981] on 8246c3cf-6607-4228-993b-4d95d33730f1

Modified: tor/branches/tor-0_1_2-patches/configure.in
===================================================================
--- tor/branches/tor-0_1_2-patches/configure.in	2007-05-25 22:00:17 UTC (rev 10343)
+++ tor/branches/tor-0_1_2-patches/configure.in	2007-05-25 23:23:18 UTC (rev 10344)
@@ -51,7 +51,15 @@
         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