Re: BUG #15789: libpq compilation with OpenSSL 1.1.1b fails on Windows with Visual Studio 2017
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
Cc: Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>, serpashk@gmail.com, pgsql-bugs@lists.postgresql.org
Date: 2019-06-26T01:48:03Z
Lists: pgsql-bugs
On Tue, Jun 25, 2019 at 11:43:29AM +0200, Juan José Santamaría Flecha wrote: > If you are using a string you will need padding, maybe mimic > OPENSSL_VERSION_NUMBER [1]. For now, I have taken the more simple approach to have three separate fields for the digit numbers, which is more than enough. So, after doing more tweaks and tests on it with the installers for 1.0.2, 1.1.0 and 1.1.1, I have committed the patch to master for now. The result is rather cool, as we can now adapt with future versions easily. I am planning to back-patch the thing down to 9.4 where OpenSSL 1.1.0 is supported, but first let's see if the buildfarm has anything to say. I don't expect any issues as we basically don't change the logic build for 1.0.2, but nobody is never careful enough with this stuff. -- Michael
Commits
-
Add support for OpenSSL 1.1.0 and newer versions in MSVC scripts
- 05b2758c39e2 9.4.24 landed
- d908a0087e0a 9.5.19 landed
- 5329606693fc 9.6.15 landed
- a559805597d5 10.10 landed
- 0e08a3a1f541 11.5 landed
- d993e0fb82ff 12.0 landed