From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
Cc: pgsql-hackers@postgresql.org
Subject: Re: plperl: update ppport.h and fix configure version check
Date: Tue, 05 Oct 2021 10:30:13 -0400
Message-ID: <4069802.1633444213@sss.pgh.pa.us> (raw)
In-Reply-To: <3548e807-ba09-290e-989b-440a5e426c3c@dunslane.net>
References: <87y278s6iq.fsf@wibble.ilmari.org>
<4028442.1633403571@sss.pgh.pa.us>
<3548e807-ba09-290e-989b-440a5e426c3c@dunslane.net>
Andrew Dunstan <andrew@dunslane.net> writes:
> Seems OK. Note that the Msys DTK perl currawong uses to build with is
> ancient (5.6.1). That's going to stay as it is until it goes completely
> out of scope in about 13 months. The perl it builds plperl against is
> much more modern - 5.16.3.
That brings up something I was intending to ask you about -- any special
tips about running the buildfarm script with a different Perl version
than is used in the PG build itself? I'm trying to modernize a couple
of my buildfarm animals to use non-stone-age SSL, but I don't really
want to move the goalposts on what they're testing.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andrew@dunslane.net, ilmari@ilmari.org
Subject: Re: plperl: update ppport.h and fix configure version check
In-Reply-To: <4069802.1633444213@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox