Horton

Re: pl/perl extension fails on Windows

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Noah Misch <noah@leadboat.com>
Cc: Dave Page <dpage@postgresql.org>, Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>, Ashutosh Sharma <ashu.coek88@gmail.com>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-11-30T04:45:35Z
Lists: pgsql-hackers 
Noah Misch <noah@leadboat.com> writes:
> On Wed, Nov 29, 2017 at 11:34:56PM -0500, Tom Lane wrote:
>> I don't really have an opinion about the relative merits of these changes,
>> but why do anything?  The existing solution has the buildfarm happy, and
>> we've not heard any field complaints that I saw.  I'm not sure we should
>> spend more time on supporting obsolete toolchain combinations that aren't
>> represented in the buildfarm.

> It's the other way around.  The buildfarm's 32-bit MSVC animals each use an
> obsolete Perl.  PostgreSQL is incompatible with today's 32-bit ActivePerl and
> Strawberry Perl.

Oh, OK.  In that case, we need to get some representatives of these
more modern builds into the buildfarm while we're at it.

			regards, tom lane

Commits

  1. MSVC: Test whether 32-bit Perl needs -D_USE_32BIT_TIME_T.

  2. Further tweaks to compiler flags for PL/Perl on Windows.

  3. Absorb -D_USE_32BIT_TIME_T switch from Perl, if relevant.

  4. PL/Perl portability fix: absorb relevant -D switches from Perl.

  5. PL/Perl portability fix: avoid including XSUB.h in plperl.c.