haproxy 2.0.0 build openssl version mismatch?

I'm building haproxy 2.0.0, git log | head commit ba23630ad009464dc8e4d01dac9ce779eb84cc2a Author: Willy Tarreau Date: Sun Jun 16 20:00:26 2019 +0200 [RELEASE] Released version 2.0.0 Released versi

Re: haproxy 2.0.0 build openssl version mismatch?

bob On Wed, Jul 17, 2019, at 8:29 AM, Zakharychev, Bob wrote: > you are using SSL_INC and SSL_LIB incorrectly: they should ONLY contain > paths to corresponding include and library directories, not GCC > options. So in your case they should look like this: > > SSL_LIB=/opt/prod/openssl111

Re: haproxy 2.0.0 build openssl version mismatch?

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.co

Re: haproxy 2.0.0 build openssl version mismatch?

bob On Wed, Jul 17, 2019, at 10:06 AM, Zakharychev, Bob wrote: > rpath is not the best solution here IMO - if the dependency is moved or > removed (or replaced with a wrong SO in the right path, maybe even > maliciously) from the system haproxy will still fail to load. I > personally simply sta

config file continuation lines?

i'm writing my config file for haproxy 2.0.0 reading through https://www.haproxy.com/blog/the-four-essential-sections-of-an-haproxy-configuration/ https://www.haproxy.org/download/2.0/doc/configuration.txt https://www.haproxy.com/documentation/hapee/1-9r1/administration/ I'm looking for i