Horton

Re: plperl: update ppport.h and fix configure version check

Andrew Dunstan <andrew@dunslane.net>

View thread View on postgr.es
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>, pgsql-hackers@postgresql.org
Date: 2021-10-06T22:58:25Z
Lists: pgsql-hackers 
On 10/5/21 10:30 AM, Tom Lane wrote:
> 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.
>
> 	


Mostly if you set the perl you're building against in the path ahead of
the perl you running with things just work. A notable exception is TAP
tests, where you have to set PROVE in the config_env to point to the
prove script you're going to use.


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com

Commits

  1. plperl: update ppport.h to Perl 5.34.0.

  2. Doc: update our claims about the minimum recommended AIX version.

  3. Update test/perl/README to insist on Perl version >= 5.8.3, too.

  4. Adjust configure to insist on Perl version >= 5.8.3.