Re: OpenSSL 3.0.0 compatibility

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: OpenSSL 3.0.0 compatibility
Date: 2020-07-16 08:58:58
Message-ID: f02c3bba-2cea-1922-7deb-2763938f71c6@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-07-13 15:38, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>>>> where would be a good place to define
>>>> OPENSSL_API_COMPAT?
>
>> Actually, it would be most formally correct to set it using AC_DEFINE in
>> configure.in, so that configure tests see it.
>
> Yeah, very good point.

New patch done that way.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
v2-0001-Define-OPENSSL_API_COMPAT.patch text/plain 3.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2020-07-16 09:14:04 Re: [POC] Fast COPY FROM command for the table with foreign partitions
Previous Message Masahiko Sawada 2020-07-16 08:15:01 Re: Resetting spilled txn statistics in pg_stat_replication