configure fails against Apache 2.4

Closing with release.

http://svn.shibboleth.net/view/cpp-sp?rev=3764&view=rev

Updated patch in proper format, and with additional fixes to 2.4 use of apr1 and apu1 options. This now works with a configure command using --enable-apache-24 and --with-apxs24 options alone.

The other bug might be why I had to fully qualify the options like I did. If you follow my example it would work without that extra change.

The warning is what it is, I have no control over what that will do to you. It simply tells you whether the compiler options used match or not. Since the SP is C++ and the server is C, they tend to be different anyway.

Fixing that case statement allowed my configure to proceed further.... however I then encountered another problem:

checking for user-specified Apache 2.4 apxs name/location... "/usr/local/apache/bin/apxs"
checking to see if Apache 2.4 apxs was located... /usr/local/apache/bin/apxs
checking for apr-1-config... ./configure: line 21124: -q: command not found
no
configure: error: Unable to locate apr-1-config, may need --with-apr1 option.

If I further modify the configure script, replacing:
21092 # If we haven't done this work already for Apache 2.2
21093 if test "$WANT_APACHE_22" != "yes" ; then
21094 # APR1 settings
with:
21092 # If we haven't done this work already for Apache 2.2
21093 if test "$WANT_APACHE_24" != "yes" ; then
21094 # APR1 settings

I've no idea whether this is really ok, but doing so results in my configure completing, although I get scary looking warning:
==================================================================
WARNING: You have chosen to compile Apache-2.4 modules with a different
compiler than the one used to compile Apache.

Current compiler: gcc
Apache's compiler: gcc -std=gnu99

This could cause problems.
==================================================================

Do you know if this is really likely to be a problem? If so, any idea how I solve it?

I can then run the make which results in mod_shib_24.so , which I can successfully include in my Apache config with the LoadModule line. I haven't got as far as trying to configure the Apache to actually use it yet though - so don't know whether it really functions.