Postgres Pro
Downloads
Home   >   mailing lists

Re: Remove deprecation warnings when compiling PG ~13 with OpenSSL 3.0~ - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Remove deprecation warnings when compiling PG ~13 with OpenSSL 3.0~
Date
Msg-id ZJKqP1VYg4AnUcTw@paquier.xyz
Whole thread Raw
In response to Re: Remove deprecation warnings when compiling PG ~13 with OpenSSL 3.0~  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Remove deprecation warnings when compiling PG ~13 with OpenSSL 3.0~
List pgsql-hackers
Tree view 
On Wed, Jun 21, 2023 at 09:16:38AM +0200, Daniel Gustafsson wrote:
> Agreed, I'd be more inclined to go with OPENSSL_API_COMPAT.  If we still get
> warnings with that set then I feel those warrant special consideration rather
> than a blanket suppression.

4d3db136 seems to be OK on REL_13_STABLE with a direct cherry-pick.
REL_11_STABLE and REL_12_STABLE require two different changes:
- pg_config.h.win32 needs to list OPENSSL_API_COMPAT.
- Solution.pm needs an extra #define OPENSSL_API_COMPAT in
GenerateFiles() whose value can be retrieved from configure.in like in
13~.

Anything I am missing perhaps?
--
Michael
Attachment

pgsql-hackers by date:

Previous
From: "Drouvot, Bertrand"
Date:
Subject: ProcessStartupPacket(): database_name and user_name truncation
Next
From: John Naylor
Date:
Subject: Re: remap the .text segment into huge pages at run time