-
Notifications
You must be signed in to change notification settings - Fork 533
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[centos-rpm] OpenSSL conflicts #161
Comments
I recall seeing another issue somewhere sorta like this... try building |
How would I go about doing that? The Luarocks documentation leaves a lot to be desired. |
This might be what I was thinking of: #36 Maybe this helps too: leafo/lapis#632
The directory is
|
No bueno. OpenResty does not provide source files and the source files provided by the system have the same backport conflict, as expected.
|
I've fixed the issue! I needed to also install RUN yum -y install openssl-devel openresty-openssl-devel
RUN luarocks install lapis CRYPTO_DIR=/usr/local/openresty/openss/ CRYPTO_INCDIR=/usr/local/openresty/openssl/include OPENSSL_DIR=/usr/local/openresty/openssl OPENSSL_INCDIR=/usr/local/openresty/openssl/include Interestingly enough, when I installed I also have the system |
I am trying to build a Docker image using openresty's official image as a base. According to the following bug report, both RedHat and Luaossl backported a feature from OpenSSL 1.2 to OpenSSL 1.1 and this double-backport is causing conflicts.
wahern/luaossl#175
The proposed solution is to supply Luaossl with additional build flags so that it doesn't try to redefine definitions already defined by RedHat:
RUN luarocks install luaossl CFLAGS="-O2 -fPIC -DHAVE_EVP_KDF_CTX=1"
This works in that Luaossl builds, but when I am trying to run my Lapis application, I get the following error:
From the error message, it appears that the
_openssl.so
provided by openresty does not have this backported feature, but the system OpenSSL, which appears to not be invoked, does?The text was updated successfully, but these errors were encountered: