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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: plperl: update ppport.h and fix configure version check
Date: 2021-10-06 22:58:25
Message-ID: b9a46b3f-3056-bd28-a4c9-acc35cfa6f99@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 10/5/21 10:30 AM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Dilger 2021-10-06 23:01:56 Re: Role Self-Administration
Previous Message Bossart, Nathan 2021-10-06 22:55:49 Re: ALTER INDEX .. RENAME allows to rename tables/views as well