>jakarta-tomcat-connectors/jk/native2/server/apache2/Makefile
>
> Index: Makefile
> ===================================================================
> RCS file:
>/home/cvs/jakarta-tomcat-connectors/jk/native2/server/apache2/M
>akefile,v
> retrieving revision 1.4
> retrieving revision 1.5
> diff -u -r1.4 -r1.5
> --- Makefile 28 Apr 2002 13:38:34 -0000 1.4
> +++ Makefile 7 May 2002 19:42:40 -0000 1.5
> @@ -26,6 +26,7 @@
> -I${JAVA_HOME}/include\hp-ux
>
> JK_CFLAGS=-DCHUNK_SIZE=4096 -DUSE_APACHE_MD5 -DHAS_APR -DHAVE_JNI
> +JK_LDFLAGS=-L${APACHE2_HOME}/lib -lapr -lcrypt
>
> ###### Based on rules.mk ##########################################
> ALL_CFLAGS = $(EXTRA_CFLAGS) $(NOTEST_CFLAGS) $(CFLAGS)
> @@ -38,7 +39,7 @@
> COMPILE = $(CC) $(ALL_CFLAGS) $(ALL_CPPFLAGS) $(ALL_INCLUDES)
>
> SH_COMPILE = $(LIBTOOL) --mode=compile $(COMPILE) $(JK_CFLAGS)
> -MOD_LINK = $(LIBTOOL) --mode=link $(CC) -module -shared
>$(LT_LDFLAGS) $(ALL_LDFLAGS)
> +MOD_LINK = $(LIBTOOL) --mode=link $(CC) -module -shared
>$(LT_LDFLAGS) $(ALL_LDFLAGS) $(JK_LDFLAGS)
>
>
>###############################################################
>##############
>
We've got a problem here with all the automake stuff added.
There is allready a Makefile.in which will scratch your Makefile
after autoconf....
BTW, you're current Makefile seems ready for autoconf/m4 processing
APACHE2_HOME, and the build.properties could be also used.
So what to do now ?
- There is a Makefile.apxs which works fine with both Apache 1.3
and Apache 2.0
- There is your Makefile and which could be processed by autoconf
(from Makefile.in to Makefile)
I'm a little puzzled here since we have now, many way to build
jk2 for apache 2.0 (and 1.3) :
jkant, Makefile (Apache 2), Makefile.apxs (AP2/AP13), and the automake
stuff.
What about using only 2 makefiles, one for dynamic (using apxs), one
for static ?
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
