From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Show version of OpenSSL in ./configure output |
Date: | 2023-10-23 07:18:58 |
Message-ID: | 502CD204-BA15-4B74-A2A7-F7E67876E995@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 23 Oct 2023, at 08:22, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
> On 23.10.23 02:26, Michael Paquier wrote:
>> 5e4dacb9878c has reminded me that we don't show the version of OpenSSL
>> in the output of ./configure. This would be useful to know when
>> looking at issues within the buildfarm, and I've wanted that a few
>> times.
Many +1's, this has been on my TODO for some time but has never bubbled to the
top. Thanks for working on this.
>> How about the attached to use the openssl command, if available, to
>> display this information? Libraries may be installed while the
>> command is not available, but in most cases I'd like to think that it
>> is around, and it is less complex than using something like
>> SSLeay_version() from libcrypto.
>> meson already shows this information, so no additions are required
>> there. Also, LibreSSL uses `openssl`, right?
>
> The problem is that the binary might not match the library, so this could be very misleading. Also, meson gets the version via pkg-config, so the result would also be inconsistent with meson. I am afraid this approach would be unreliable in the really interesting cases.
I tend to agree with this, it would be preferrable to be consistent with meson
if possible/feasible.
--
Daniel Gustafsson
From | Date | Subject | |
---|---|---|---|
Next Message | Jeevan Chalke | 2023-10-23 07:20:55 | Re: More new SQL/JSON item methods |
Previous Message | Drouvot, Bertrand | 2023-10-23 06:50:45 | Re: Synchronizing slots from primary to standby |