Re: Remove deprecation warnings when compiling PG ~13 with OpenSSL 3.0~
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Andres Freund <andres@anarazel.de>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-06-21T07:43:59Z
Lists: pgsql-hackers
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
Commits
-
Define OPENSSL_API_COMPAT
- 96f96398d398 11.21 landed
- 265c9138da58 12.16 landed
- 8aa9a26236aa 13.12 landed
-
Remove support for OpenSSL versions older than 0.9.8.
- 9b7cd59af1af 10.0 cited