Closed Fallen-Zen-zz closed 9 years ago
you should rely on the default system SSL version - compiling you're own version can cause deployment issues with SSL incompatibilities.
daaang - someone need to close this thread .
Amazingly I came across this issue in 2021 still.
I checked where passenger was looking for open ssl by passing the VERBOSE = 1
option
after that I linked openssl to one of the folders listed:
sudo ln -s /opt/homebrew/opt/openssl@1.1/include/openssl /opt/local/include/openssl
On Debian 11, I solved with the following env vars:
export EXTRA_CFLAGS=-I/usr/local/src/openssl-1.1.1c/include && \
export EXTRA_CXXFLAGS=-I/usr/local/src/openssl-1.1.1c/include && \
export EXTRA_LDFLAGS=-L/usr/local/src/openssl-1.1.1c && \
passenger-install-apache2-module
After upgrading to El Capitan I'm unable to install the Apache module by running
passenger-install-apache2-module
.I'm getting this error:
* Checking for OpenSSL development headers... Found: no
There's for sure a default installation of OpenSSL on the system, also tried installing the latest one (OpenSSL 1.0.2d 9 Jul 2015) to
/opt/local/bin/openssl
but that did not help at all. Still the same problem.How can I point to the correct path?