Re: OpenSSL 3.0.0 compatibility - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: OpenSSL 3.0.0 compatibility
Date
Msg-id 7d44559a-5db1-1bbb-0419-eb14c74f2488@2ndquadrant.com
Whole thread Raw
In response to Re: OpenSSL 3.0.0 compatibility  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: OpenSSL 3.0.0 compatibility  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2020-07-07 22:52, Daniel Gustafsson wrote:
>>> where would be a good place to define
>>> OPENSSL_API_COMPAT?  The only place that's shared between frontend and
>>> backend code is c.h.  The attached patch does it that way.
>> pg_config_manual.h, perhaps?
> I don't have a strong preference.  When starting hacking on this I went for the
> quick and simple option of adding it to CFLAGS in configure.in for the time
> being since I wasn't sure where to put it.

Actually, it would be most formally correct to set it using AC_DEFINE in 
configure.in, so that configure tests see it.  It doesn't look like we 
currently have any configure tests that would really be affected, but it 
seems sensible to do it there anyway.

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



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: [PATCH] Performance Improvement For Copy From Binary Files
Next
From: Michael Paquier
Date:
Subject: Re: Don't choke on files that are removed while pg_rewind runs.