Re: Compilation issues with 1.6.2 and filter/apache2

[johanna bromberg craig <canna@xxxxxxxxx>]

Hey Steve,

As Dan mentioned, the 2 typos are fixed in CVS and will be incorporated 
into 1.7, which will be released in the next week.

As to the Apache 1.3 vs Apache 2, I've just changed the behavior of 
configure so you now can specify if you want to
	--enable-apache1=[explicit path to apache 1.3 apxs ] and/or
	--enable-apache2=[explicit path to apache 2 apxs

They work separately and together, but at least one must be specified 
explicitly otherwise cosign won't build.

As to the apxs errors with Apache 2 - despite the errors, which we have 
yet to track down, the filter does run fine. We don't happen to run the 
Apache 2 filter in production here at ITCS ( as we have no production 
Apache 2 machines at all), though I think Lane Hoy at Dentistry was 
looking into it.

Other schools - University of Auckland, for sure, and possibly either 
Penn State or University of Edinburgh are running the 2.x filter - 
perhaps they can comment?

Let us know if you have any further questions.

-J


On Oct 6, 2004, at 11:32 AM, Steve Simmons wrote:

> Two items -
>
> The download page for cosign says that apache2 is not supported; the
> roadmap page (http://www.umich.edu/~umweb/software/cosign/roadmap.html)
> says it was supported as of v1.5.  Which is correct?
>
> Has anyone out there successfully build 1.6.2 for apache2 'out of the
> box'?  I have encountered three show-stoppers and an interesting 
> warning.
>
> Config:   ./configure --enable-apache2=/usr/local/apache/bin/apxs
> Environment:  CPPFLAGS=""-I/usr/local/apache/include", gcc 3.3.2, 
> solaris 8,
>     /usr/local/apache is a symlink to /usr/local/apache-2.0.46
>
> The most serious is a syntax error in filters/apache2/mod_cosign.c,
> lines 780/781, where a string literal is broken into two lines exactly
> on an 80-char boundary.
>
> The Makefile generated also has a problem. filters/apache2/Makefile.in
> is missing a space on line 20, where
>      ..._DB=\"${FILTERDB}\"-D_COSIGN_...
> should be
>      ..._DB=\"${FILTERDB}\" -D_COSIGN_...
>
> Finally, the toplevel Makefile always seems to want to build both
> apache1 and apache2 filters.  That seems clearly wrong, but it's
> hardwired in the Makefile.in.  Apache 1 filters builds failed in
> this configuration, but that would seem to be reasonable given we're
> specifying apache2 include files.  I simply removed all the
> filter/apache dir references from the final Makefile.
>
> With these fixes the filter compiles, but the last step yields this
> warning (lines broken by me for readability):
>
>     /usr/local/apache-2.0.46/build/libtool --silent --mode=link \
> 	gcc -o mod_cosign.la  -rpath /usr/local/apache-2.0.46/modules \
> 	-module -avoid-version    mod_cosign.o connect.o cookiefs.o \
> 	sparse.o ../../common/argcargv.o ../../common/fbase64.o \
> 	../../common/mkcookie.o ../../version.o -L../../libsnet/ \
> 	-L/usr/pkg/lib -lsnet
>
>     *** Warning: Linking the shared library mod_cosign.la against \
>         the non-libtool
>     *** objects  mod_cosign.o connect.o cookiefs.o sparse.o \
>         ../../common/argcargv.o ../../common/fbase64.o \
> 	../../common/mkcookie.o ../../version.o is not portable!
>     make[1]: Leaving directory 
> `/afs/sph.umich.edu/sys/src/apache/cosign-1.6.2/filters/apache2'
>
>
> Given the warning and other surprises I'm not confident about dropping
> the compiled filter into our apache2 tree; comments from others using
> this would for apache2 would be appreciated.
>
> Steve
>
> !DSPAM:416410f0323131730242369!