On 20.02.2014 04:18, William A. Rowe Jr. wrote:
> Can anyone offer background as to why httpd 2.4 branch ./configure likes
>
> checking for OpenSSL... checking for user-provided OpenSSL base
> directory... /usr/local/ssl adding "-I/usr/local/ssl/include" to
> CPPFLAGS setting MOD_CFLAGS to "-I/usr/local/ssl/include "
> setting ab_CFLAGS to "-I/usr/local/ssl/include "
> setting MOD_LDFLAGS to "-L/usr/local/ssl/lib "
> checking for OpenSSL version >= 0.9.8a... OK
> adding "-lssl" to MOD_LDFLAGS
> adding "-lcrypto" to MOD_LDFLAGS
> adding "-luuid" to MOD_LDFLAGS
> adding "-lrt" to MOD_LDFLAGS
> adding "-lcrypt" to MOD_LDFLAGS
> adding "-lpthread" to MOD_LDFLAGS
> adding "-ldl" to MOD_LDFLAGS
> setting LIBS to "-lssl -lcrypto -luuid -lrt -lcrypt -lpthread -ldl"
> forcing ab_LDFLAGS to "-L/usr/local/ssl/lib -lssl -lcrypto -luuid
> -lrt -lcrypt -lpthread -ldl"
>
> instead of MOD_SSL_CFLAGS, MOD_SSL_LDFLAGS, and MOD_SSL_LIBS?
This was added with r1385216, to support per-subdir MOD_* variables,
see the discussion starting at [1]. Previously, there was no way for a
module to make sure that its specific {C,LD}FLAGS were inserted first.
Kaspar
[1]
https://mail-archives.apache.org/mod_mbox/httpd-dev/201208.mbox/%3C502D3DAF.2010402%40velox.ch%3E
