Skip site navigation (1) Skip section navigation (2)

Re: Testing plperl<->plperlu interaction

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, decibel <decibel(at)decibel(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Testing plperl<->plperlu interaction
Date: 2010-01-09 01:20:09
Message-ID: 24937.1263000009@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> OK, here is a patch that provides for running regression tests for 
> plperlu alone and plperl/plperlu interaction, skipping the latter if 
> it's not supported on the platform, using the test Tim has suggested.

> ! ifeq ($(shell $(PERL) -V:usemultiplicity), usemultiplicity='define';)
> ! 	REGRESS += plperl_plperlu
> ! endif

Hm ... I wonder how badly this fails if perl isn't present?

Before you say that that won't matter, consider "make clean" etc.
The makefile does have to parse.

It might be sufficient to wrap this test in an "ifneq ($(PERL),)"
or similar.

Also, some commentary connecting this test to plperl.c's support for
two interpreters would be a good thing.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Greg StarkDate: 2010-01-09 01:38:22
Subject: Re: Streaming replication status
Previous:From: Greg StarkDate: 2010-01-09 01:14:29
Subject: Re: synchronized snapshots

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group