Re: mod_ssl openssl ./configure particularity
On 22.02.2014 18:56, William A. Rowe Jr. wrote: Understood and this would explain assigning them to MOD_SSL_LIBS etc. But added to MOD_LIBS? That struck me as very odd. Putting a module prefix into the variable name would make assembling the commands in build/rules.mk more complex, and it seemed unnecessary at the time. The MOD_* variables end up in modules.mk in the module's subdir, so they don't interfere with each other. Kaspar
Re: mod_ssl openssl ./configure particularity
Understood and this would explain assigning them to MOD_SSL_LIBS etc. But
added to MOD_LIBS? That struck me as very odd.
On Feb 22, 2014 1:41 AM, Kaspar Brand httpd-dev.2...@velox.ch wrote:
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
Re: mod_ssl openssl ./configure particularity
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
mod_ssl openssl ./configure particularity
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?
