On Wed, Jul 17, 2019, at 9:13 AM, Aleksandar Lazic wrote:
>
> Can you try to adopt your system to the openssl path as I in the dockerfile.
>
> https://gitlab.com/aleks001/haproxy20-centos/blob/master/Dockerfile#L37
>
> ```
> echo "/opt/prod/openssl111c/lib64" > /etc/ld.so.conf.d/openssl-111c.conf \
> && ldconfig -v \
> ```
ldconfig additions/changes are system-wide, and local environment specific --
and subject to end-user override.
does haproxy simply support rpath -- which correctly solves the linking problem
in the distributed package by hardcoding the specified/intended runtine path --
like most other packages?
e.g., all rpath'd &/or config-managed build/installs,
ldd `which nginx` | egrep "ssl|crypto"
libssl.so.1.1 => /opt/prod/openssl111c/lib64/libssl.so.1.1
(0x00007f24ae9f6000)
libcrypto.so.1.1 =>
/opt/prod/openssl111c/lib64/libcrypto.so.1.1 (0x00007f24ae4f0000)
ldd `which php` | egrep "ssl|crypto"
libssl.so.1.1 => /opt/prod/openssl111c/lib64/libssl.so.1.1
(0x00007f4c1533a000)
libcrypto.so.1.1 =>
/opt/prod/openssl111c/lib64/libcrypto.so.1.1 (0x00007f4c14e34000)
ldd `which mariadb` | egrep "ssl|crypto"
libssl.so.1.1 => /opt/prod/openssl111c/lib64/libssl.so.1.1
(0x00007feb8998a000)
libcrypto.so.1.1 =>
/opt/prod/openssl111c/lib64/libcrypto.so.1.1 (0x00007feb89484000)
ldd `which named` | egrep "ssl|crypto"
libssl.so.1.1 => /opt/prod/openssl111c/lib64/libssl.so.1.1
(0x00007f539d468000)
libcrypto.so.1.1 =>
/opt/prod/openssl111c/lib64/libcrypto.so.1.1 (0x00007f539cf62000)
ldd `which openvpn` | egrep "ssl|crypto"
libssl.so.1.1 => /opt/prod/openssl111c/lib64/libssl.so.1.1
(0x00007fd1d891b000)
libcrypto.so.1.1 => /opt/prod/openssl111c/lib64/libcrypto.so.1.1
(0x00007fd1d8415000)
ldd `which curl` | egrep "ssl|crypto"
libssl.so.1.1 => /opt/prod/openssl111c/lib64/libssl.so.1.1
(0x00007f5085647000)
libcrypto.so.1.1 =>
/opt/prod/openssl111c/lib64/libcrypto.so.1.1 (0x00007f5085149000)
etc etc
none of which need ldconfig.
