чт, 4 нояб. 2021 г. в 22:31, Shawn Heisey <hapr...@elyograg.org>:
> On 11/4/21 7:55 AM, Willy Tarreau wrote: > > Normally you just have to specify SSL_INC and SSL_LIB at build time to > > specify the one you want to build with. I'm doing exactly this when I > > want to build with older versions: > > > I tried this. My make command (building 2.4.8) had these env additions: > > SSL_INC=/usr/include/openssl \ > SSL_LIB=/usr/lib/x86_64-linux-gnu \ > > Which should have told it to use the openssl provided by Ubuntu > packages. But that didn't work, it still found the 3.x version in > /usr/local (installed with openssl default locations for ./Configure), > and failed to compile. > > I thought I found an error in the Makefile where setting USE_OPENSSL > clears SSL_INC and SSL_LIB, but even with that problem handled (I think > ... my Makefile experience is slim), it STILL finds the 3.x version and > tries to use it. > it does not clear. at least gnu make and bsd make. SSL_INC= means "if SSL_INC is defined as environment variable, clear it", but if you specify SSL_INC from make command line, it has priority over Makefile > > Changing the prefix on the openssl compile to something nonstandard > (/usr/local/ssl3 in my case) is the only way I have found to keep the > haproxy build from finding it. This is less than ideal, but sufficient > for my needs. > > Thanks, > Shawn > > > >
