difficulty building shibboleth SP from source on RHEL6 for Apache 2.4

[Paul Beckett (ITCS)]

I've corrected my rpmbuild to use --with-apxs24:

rpmbuild --rebuild --without builtinapache -D 'shib_options --with-apxs24=/usr/local/apache/bin/apxs --enable-apache-24 --with-openssl=/usr/local/openssl' shibboleth-2.5.0-2.1.el6.src.rpm

But it still fails, with a fairly similar error message:

checking if default apache needed... yes
checking for apxs2... no
checking for apxs... /usr/local/apache/bin/apxs
checking default apache version... configure: error: unusable apache versions: . Try setting --with-apxs
error: Bad exit status from /var/tmp/rpm-tmp.0qfXFV (%build)


RPM build errors:
    line 14: prereq is deprecated: PreReq:              xmltooling-schemas(x86-64) >= 1.5.0, opensaml-schemas(x86-64) >= 2.5.0
    Bad exit status from /var/tmp/rpm-tmp.0qfXFV (%build)



I'm a bit suspicious about "checking if default apache needed... yes", is it trying to use the OS apache (which doesn't exist)?


The main reason I built openSSL from source, was so that I could have the newer TLSv1.2 protocols available (which aren't supported in the earlier RHEL6 version). I figured as I was taking the decision to build HTTPD from source (for a number of performance and feature improvements it offered over 2.2) I would have to rebuild that to keep it up-to-date, it didn't seem too much extra effort to have to rebuild openSSL from time to time.

Thanks,
Paul




>That's the same error, so that means it's more or less workable. You're
>using the wrong apxs option, it should be --with-apxs24.
>
>I'll review the configure messages to see if they're improvable, or you
>can file a bug so I remember to check them.
>
>I wouldn't really advise using a custom OpenSSL. While that gets you
>more
>features it also means you're stuck keeping it up to date. Is there some
>reason you're doing that?
>
>-- Scott