Created attachment 23302 [details] Config.log of apache-2.2.11 I ran into error while compiling apache-2.2.11. Error message: Error, SSL/TLS libraries were missing or unusable Here are the last lines before the error (details see config.log): checking openssl/engine.h usability... yes checking openssl/engine.h presence... yes checking for openssl/engine.h... yes checking for SSLeay_version... no checking for SSL_CTX_new... no checking for ENGINE_init... no checking for ENGINE_load_builtin_engines... no checking for SSL_set_cert_store... no configure: error: ... Error, SSL/TLS libraries were missing or unusable In the config.log, you can see that ld gets an error while checking SSLeay_version: configure:15034: checking for SSLeay_version configure:15090: gcc -o conftest -g -O2 -pthread -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/www/jamba/src/openssl-0.9.8j/include -L/www/hans/src/openssl-0.9.8j/lib conftest.c -lm -lssl -lcrypto -lrt -lcrypt -lpthread -ldl >&5 /usr/bin/ld: cannot find -lssl collect2: ld returned 1 exit status But in apache-2.2.9 this works without errors: configure:15062: checking for SSLeay_version in -lcrypto configure:15097: gcc -o conftest -g -O2 -pthread -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -L/www/hans/src/openssl-0.9.8j conftest.c -lcrypto -lm -lrt -lcrypt -lpthread -ldl >&5 configure:15104: $? = 0 configure:15125: result: yes Installing the Debian package "libssl-dev" will fix that, but this should also work with openssl source package. It seems that the path to openssl source generally works: configure:14916: gcc -c -g -O2 -pthread -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/www/hans/src/openssl-0.9.8j/include conftest.c >&5 configure:14923: $? = 0 In the attachment, you can find the config.log of apache-2.2.9 (config.log_2.2.9) and apache-2.2.11 (config.log_2.2.9). Thanks..
Created attachment 23303 [details] config.log of apache-2.2.9
Ok, i found the error. Setting the following environment variables fix this issuee: export LD_LIBRARY_PATH="/www/hans/src/openssl-0.9.8j/" export LIBS="-L/www/hans/src/openssl-0.9.8j" export CPPFLAGS="-I/www/hans/src/openssl-0.9.8j/include/openssl"
Thanks for the update. Do you think this problem could have been prevented by some improvement in the documentation, and if so, what would you suggest?
I don't think that this have to be updated in the documentation. stange is, that apache-2.2.9 is able compile without setting this variables while apache-2.2.11 is failed. It seems that the style of checking the SSLeay_version is the reason for that. In Version 2.2.9 it was checked by gcc -o conftest -g -O2 -pthread -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -L/www/hans/src/openssl-0.9.8j conftest.c -lcrypto -lm -lrt -lcrypt -lpthread -ldl >&5 In Version 2.2.11 it is checked by: gcc -o conftest -g -O2 -pthread -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/www/jamba/src/openssl-0.9.8j/include -L/www/hans/src/openssl-0.9.8j/lib conftest.c -lm -lssl -lcrypto -lrt -lcrypt -lpthread -ldl >&5 Possible solution could be to check this without -lssl Flag, which cause this error. Another solution is, to set these variables in configure Script, because the Path to ssl will pass through the --with-ssl Parameter
Will this be modified in the next Version of Apache?
This bug still occur during configure of apache 2.2.25 with openssl 1.0.1e. I've read from google search that you can solve this bug by using this environment: # LDFLAGS="-ldl" ./configure [...]
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.