aboutsummaryrefslogtreecommitdiffstats
path: root/include/asterisk
diff options
context:
space:
mode:
authorrizzo <rizzo@f38db490-d61c-443f-a65b-d21fe96a405b>2006-04-14 13:54:53 +0000
committerrizzo <rizzo@f38db490-d61c-443f-a65b-d21fe96a405b>2006-04-14 13:54:53 +0000
commitf9d382fc079246930a99640d7835d6ae3e4149db (patch)
treee1581eba4720d73c3c4af1012e8167a5bebd572c /include/asterisk
parent79aff8b4f416427a823e322f304933867ab0d962 (diff)
temporarily revert the way mutex are initialized on BSD systems.
This fixes the compilation on OS/X (the change exposed a wrong assumption on mutex types on OS/X), but still leaves open the bugs in initializing mutex on bsd systems, which you will see reported as 'locking failures' on certain operations. I need to investigate the issue further, but the best thing i can do now is leave things as they have been for months. git-svn-id: http://svn.digium.com/svn/asterisk/trunk@19973 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'include/asterisk')
-rw-r--r--include/asterisk/lock.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/asterisk/lock.h b/include/asterisk/lock.h
index e4276dd7f..97deac143 100644
--- a/include/asterisk/lock.h
+++ b/include/asterisk/lock.h
@@ -94,7 +94,7 @@
#endif
#ifdef BSD
-#if 0 && defined( __GNUC__)
+#if 1 && defined( __GNUC__)
#define AST_MUTEX_INIT_W_CONSTRUCTORS
#else
#define AST_MUTEX_INIT_ON_FIRST_USE