jerenkrantz 01/07/09 16:14:36
Modified: . configure.in
Log:
As discussed on [EMAIL PROTECTED] (no feedback - may have gotten lost in
shuffle?),
switch the priority of the pthread mutex to be the "best" one if it
satisfies all stated conditions (which includes the existance of
/dev/zero which will preclude the pthread mutex from being used on
HP-UX and OS/390 - which was Jeff Trawick's original concern).
Revision Changes Path
1.333 +2 -2 apr/configure.in
Index: configure.in
===================================================================
RCS file: /home/cvs/apr/configure.in,v
retrieving revision 1.332
retrieving revision 1.333
diff -u -r1.332 -r1.333
--- configure.in 2001/07/09 02:30:44 1.332
+++ configure.in 2001/07/09 23:14:33 1.333
@@ -994,12 +994,12 @@
APR_DECIDE(USE_SYSVSEM_SERIALIZE, [SysV IPC semget()]))
APR_IFALLYES(func:flock define:LOCK_EX,
APR_DECIDE(USE_FLOCK_SERIALIZE, [4.2BSD-style flock()]))
+APR_IFALLYES(header:fcntl.h define:F_SETLK,
+ APR_DECIDE(USE_FCNTL_SERIALIZE, [SVR4-style fcntl()]))
# note: the current APR use of shared mutex requires /dev/zero
APR_IFALLYES(header:pthread.h define:PTHREAD_PROCESS_SHARED dnl
func:pthread_mutexattr_setpshared file:/dev/zero,
APR_DECIDE(USE_PROC_PTHREAD_SERIALIZE, [pthread mutex]))
-APR_IFALLYES(header:fcntl.h define:F_SETLK,
- APR_DECIDE(USE_FCNTL_SERIALIZE, [SVR4-style fcntl()]))
if test "x$apr_lock_method" != "x"; then
APR_DECISION_FORCE($apr_lock_method)
fi
