From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
cc: =?UTF-8?Q?Dagfinn_Ilmari_Manns=c3=a5ker?= <ilmari@ilmari.org>,
        pgsql-hackers@postgresql.org
Subject: Re: plperl: update ppport.h and fix configure version check
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>
Comments: In-reply-to Andrew Dunstan <andrew@dunslane.net>
	message dated "Tue, 05 Oct 2021 10:17:46 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4069801.1633444213.1@sss.pgh.pa.us>
Date: Tue, 05 Oct 2021 10:30:13 -0400
Message-ID: <4069802.1633444213@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/4069802.1633444213%40sss.pgh.pa.us>
Precedence: bulk

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