Re: pg_config.h.win32 missing a set of flags from pg_config.h.in added in v11 development

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: Christian Ullrich <chris(at)chrullrich(dot)net>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org>, buildfarm(at)sraoss(dot)co(dot)jp, dpage(at)postgresql(dot)org
Subject: Re: pg_config.h.win32 missing a set of flags from pg_config.h.in added in v11 development
Date: 2018-06-13 00:07:20
Message-ID: 20180613000720.GB3138@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 12, 2018 at 04:51:59PM -0400, Andrew Dunstan wrote:
> On 06/12/2018 10:51 AM, Andrew Dunstan wrote:
>> meanwhile, Bowerbird (MSVC) is on 1.0.1d, lorikeet (Cygwin64) is on
>> 1.0.2d and jacana (Mingw) doesn't build with openssl.
>>
>> I will look at upgrading bowerbird ASAP.
>
> Well, that crashed and burned. What versions of openssl are we supporting?

What kind of failures are you seeing? I just compiled Postgres two days
ago with MSVC and OpenSSL 1.0.2o (oldest version with a Windows
installer I could find), and that was able to compile. On HEAD, OpenSSL
should be supported down to 0.9.8. This thread discusses about whether
we want to enforce HAVE_X509_GET_SIGNATURE_NID unconditionally or not,
as it is disabled now. Even if the code is linked to 1.0.2 and the flag
is not set, then the code should be able to compile.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Haribabu Kommi 2018-06-13 01:42:14 Re: Does logical replication supports cross platform servers?
Previous Message Michael Paquier 2018-06-13 00:00:47 Re: [bug fix] Cascaded standby cannot start after a clean shutdown