Re: plperl: update ppport.h and fix configure version check
От | Andrew Dunstan |
---|---|
Тема | Re: plperl: update ppport.h and fix configure version check |
Дата | |
Msg-id | b9a46b3f-3056-bd28-a4c9-acc35cfa6f99@dunslane.net обсуждение исходный текст |
Ответ на | Re: plperl: update ppport.h and fix configure version check (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: plperl: update ppport.h and fix configure version check
|
Список | 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
В списке pgsql-hackers по дате отправления: