Question - is gump building against apache 2 trunk or against the
httpd/branches/2.0.x (or some other particular httpd snapshot/rev)?

The failure below...

Making all in apache-2.0
make[1]: Entering directory 
`/x1/gump/public/workspace/jakarta-tomcat-connectors/jk/native/apache-2.0'
/usr/local/gump/public/workspace/apr/dest-16092005/build-1/libtool --silent 
--mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-16092005/include -g -O2 
-DUSE_APACHE_MD5 -I ../common  -I /opt/jdk1.4/include -I 
/opt/jdk1.4/include/unix -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE 
-D_LARGEFILE64_SOURCE -g -O2 -pthread -DHAVE_APR  
-I/usr/local/gump/public/workspace/apr/dest-16092005/include/apr-1 
-I/usr/local/gump/public/workspace/apr-util/dest-16092005/include/apr-1 -g -O2 
-g -O2 -pthread -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -c 
mod_jk.c -o mod_jk.lo
mod_jk.c:85:28: #if with no expression

didn't jive with my expectations below, unless AP_NEED_SET_MUTEX_PERMS
was actually defined, and it shouldn't be defined on 2.0.x.  I'm going
to propose the patch today to define AP_NEED_SET_MUTEX_PERMS to 1, and
then move forward to define it 0 everywhere else on httpd 2.1.x and beyond. I'll propose today so if we are fetching up 2.1+ to build
against, this problem should be resolved.  The code (the final #if was
the one which had 'no expression').

/* Yes; sorta sucks - with luck we will clean this up before httpd-2.2
 * ships, leaving AP_NEED_SET_MUTEX_PERMS def'd as 1 or 0 on all platforms.
 */
#ifdef AP_NEED_SET_MUTEX_PERMS
# define JK_NEED_SET_MUTEX_PERMS AP_NEED_SET_MUTEX_PERMS
#else
  /* A special case for httpd-2.0 */
# if !defined(OS2) && !defined(WIN32) && !defined(BEOS) && !defined(NETWARE)
#  define JK_NEED_SET_MUTEX_PERMS 1
# else
#  define JK_NEED_SET_MUTEX_PERMS 0
# endif
#endif

#if JK_NEED_SET_MUTEX_PERMS
#include "unixd.h"      /* for unixd_set_global_mutex_perms */
#endif

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to