Re: BUG #15789: libpq compilation with OpenSSL 1.1.1b fails on Windows with Visual Studio 2017

From: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
To: serpashk(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15789: libpq compilation with OpenSSL 1.1.1b fails on Windows with Visual Studio 2017
Date: 2019-05-28 05:31:55
Message-ID: CAC+AXB1Vw81MzWAPNmvpQhr_dDezucA1xu_JB9-asxzOk0rGYA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, May 2, 2019 at 3:58 PM PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:

>
> This question was raised in the following thread:
>
> https://www.postgresql.org/message-id/flat/CAAw-Mseg9JYpp%3DA%3D51HR3rKiQtbvT0MWw%2BaYFwNeJEbdNr%3DCDA%40mail.gmail.com
>
> No solution was proposed.
>
>
Can you check if you get a sane compilation with the attached patch?

It is just a compilation issue, once the software is built with the 1.1.x
libraries you should not have any further problems to use SSL.

Regards,

Juan José Santamaría Flecha

Attachment Content-Type Size
0001_windows_openssl_1.1.0_build_v11.patch application/x-patch 3.7 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Billen 2019-05-28 09:56:03 psql should re-read connection variables after connection reset
Previous Message PG Bug reporting form 2019-05-27 16:11:37 BUG #15821: Parallel Workers with functions and auto_explain: ERROR: could not find key 3 in shm TOC