apr-util crypto support fails when apr-util is in a custom location

[quanah]

This is likely similar to issue#882

When apr-util is installed into a custom location (such as /opt/zimbra/common), crypto detection fails, even though the crypto header exists:

build@c690:~/p4/zimbra/main/ThirdParty/modsecurity/tmp/RHEL6_64/zimbra-modsecurity/rpm/BUILD/modsecurity-2.9.0$ ls /opt/zimbra/common/include/apr-1/apr_crypto.h
/opt/zimbra/common/include/apr-1/apr_crypto.h

It appears the APU_INCLUDEDIR is not set correctly:

APU_INCLUDEDIR=''

APXS flags are set correctly:

APXS_INCLUDES='-I/opt/zimbra/common/include -I/opt/zimbra/common/include -I. -I/opt/zimbra/common/include/apr-1 -I/opt/zimbra/common/include'

build@c690:/p4/zimbra/main/ThirdParty/modsecurity/tmp/RHEL6_64/zimbra-modsecurity/rpm/BUILD/modsecurity-2.9.0$ /opt/zimbra/common/bin/apr-1-config --includedir
/opt/zimbra/common/include/apr-1
build@c690:/p4/zimbra/main/ThirdParty/modsecurity/tmp/RHEL6_64/zimbra-modsecurity/rpm/BUILD/modsecurity-2.9.0$ /opt/zimbra/common/bin/apu-1-config --includedir
/opt/zimbra/common/include/apr-1

[quanah]

Ok, this is related to issue #900

If I add --disable-mlogc, it no longer can find apr and apu