From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Make finding openssl program a configure or meson option |
Date: | 2022-10-13 10:29:36 |
Message-ID: | 2f466b7e-7651-0a83-5c38-ace852e7834e@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12.10.22 03:08, Michael Paquier wrote:
> On Tue, Oct 11, 2022 at 05:06:22PM +0200, Peter Eisentraut wrote:
>> Various test suites use the "openssl" program as part of their setup. There
>> isn't a way to override which openssl program is to be used, other than by
>> fiddling with the path, perhaps. This has gotten increasingly problematic
>> with some of the work I have been doing, because different versions of
>> openssl have different capabilities and do different things by default.
>> This patch checks for an openssl binary in configure and meson setup, with
>> appropriate ways to override it. This is similar to how "lz4" and "zstd"
>> are handled, for example. The meson build system actually already did this,
>> but the result was only used in some places. This is now applied more
>> uniformly.
>
> openssl-env allows the use of the environment variable of the same
> name. This reminds me a bit of the recent interferences with GZIP,
> for example.
Sorry, what is "openssl-env"? I can't find that anywhere.
> This patch is missing one addition of set_single_env() in
> vcregress.pl, and one update of install-windows.sgml where all the
> supported environment variables for commands are listed.
Ok, I'll add that.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2022-10-13 10:37:39 | Re: Suppressing useless wakeups in walreceiver |
Previous Message | Peter Eisentraut | 2022-10-13 10:26:32 | Re: Allow tests to pass in OpenSSL FIPS mode |