> On 15 Feb 2022, at 14:12, Juan José Santamaría Flecha
> wrote:
> After has been included, any inclusion of
> will be troublesome.
Not that it changes anything here, but FTR: in OpenSSL 3.0.0 and onwards this
undef has been moved to
--
Daniel Gustafsson https://vmware.com
On Fri, Feb 11, 2022 at 4:36 PM Tom Lane wrote:
> =?UTF-8?Q?Juan_Jos=C3=A9_Santamar=C3=ADa_Flecha?= <
> juanjo.santama...@gmail.com> writes:
> > There is a comment in 'src/backend/libpq/be-secure-openssl.c' addressing
> > this issue, but I have to explicitly undefine X509_NAME. Please find
> > at
=?UTF-8?Q?Juan_Jos=C3=A9_Santamar=C3=ADa_Flecha?=
writes:
> There is a comment in 'src/backend/libpq/be-secure-openssl.c' addressing
> this issue, but I have to explicitly undefine X509_NAME. Please find
> attached a patch for so.
Um ... why? Shouldn't the #undef in the OpenSSL headers take car
Hello,
When building Postgres using MSVC with Kerberos Version 4.1 and OpenSSL
1.1.1l (both of them, using only one will raise no errors), I see errors
like:
"C:\postgres\pgsql.sln" (default target) (1) ->
"C:\postgres\postgres.vcxproj" (default target) (2) ->
(ClCompile target) ->
C:\postgres\
