From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | 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 06:22:25 |
Message-ID: | 4c8ce113-76ba-4587-a23f-11ebe4f1b38b@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
>
> 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.
> + # Print version of OpenSSL, if command is available.
> + AC_ARG_VAR(OPENSSL, [path to openssl command])
> + PGAC_PATH_PROGS(OPENSSL, openssl)
There is already a call like this in configure.ac, so (if this approach
is taken) you should rearrange things to make use of that one.
> + pgac_openssl_version="$($OPENSSL version 2> /dev/null || echo no)"
> + AC_MSG_NOTICE([using openssl $pgac_openssl_version])
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2023-10-23 06:30:28 | Add trailing commas to enum definitions |
Previous Message | Hayato Kuroda (Fujitsu) | 2023-10-23 05:39:59 | RE: [PoC] pg_upgrade: allow to upgrade publisher node |