Hi there,
in trunk there's a detection whether OpenSSL can use &errno as a
THREADID. It was added almost 10 years ago in r1791055.
The program used to check for the feature uses APR headers and links
against APR trying to run the result. When APR is not already in the
system path, this fails. For instance on my system, because the compiled
test binary can not load APR due to missing RPATH. If there is no
installed APR lib on the build system when running configure, that test
will also fail.
I can work around this when building on my systems, but I wonder,
whether it is a non-pattern to actually use APR during httpd configure
tests. It looks like this test is the only one doing this.
No idea, whether a simpler detection without APR is easily doable.
The feature is used via AP_OPENSSL_USE_ERRNO_THREADID and then
DEFAULT_THREADID_IS_SAFE in modules/ssl/ssl_util.c (only in trunk).
Best regards,
Rainer
