From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Konstantin Izmailov <pgfizm(at)gmail(dot)com> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: is libpq and openssl 1.1.* compatible? |
Date: | 2018-02-26 08:15:59 |
Message-ID: | 20180226081559.GC1960@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Feb 26, 2018 at 12:30:38AM -0700, Konstantin Izmailov wrote:
> Let me ask this differently: can Visual Studio 2013/2017 compile libpq with
> openssl 1.1 support? Under Windows?
The answer to this question should be yes. (Please note that no
Windows buildfarm machines use openssl 1.1.0 as far as I can see, I
myself build stuff with 1.0.2 on Windows.)
> I have not been able to find an answer by googling before asking this
> question here. Can someone share the compiled library and changes in the
> source if needed for the openssl 1.1? Magnus please.
No changes should be needed as far as I know in the scripts in
src/tools/msvc. The set of APIs present in 1.1.0 is the same whatever
the platform so the compatibility is the same, and the dependent
libraries should be ssleay32.lib and libeay32.lib whose location depend
on your installation of OpenSSL.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2018-02-26 10:15:44 | Re: Unexpected behavior with transition tables in update statement trigger |
Previous Message | Konstantin Izmailov | 2018-02-26 07:30:38 | Re: is libpq and openssl 1.1.* compatible? |