plperl fails with perl 5.14.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Cc: marti(at)juffo(dot)org
Subject: plperl fails with perl 5.14.0
Date: 2011-06-04 16:30:09
Message-ID: 26174.1307205009@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

It appears from the buildfarm configure logs that member anchovy was
updated yesterday from perl 5.12.3 to 5.14.0. It doesn't like plperl.c
anymore:

ccache cc -flto -march=amdfam10 -fstack-protector -O3 -pipe -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wformat-security -fno-strict-aliasing -fwrapv -g -fpic -I. -I. -I../../../src/include -D_GNU_SOURCE -I/usr/include/libxml2 -I/usr/lib/perl5/core_perl/CORE -c -o plperl.o plperl.c
plperl.c: In function 'plperl_trusted_init':
plperl.c:929:36: error: lvalue required as left operand of assignment
make[3]: *** [plperl.o] Error 1

What it's unhappy about is evidently this:

GvCV(sv) = NULL; /* prevent call via GV */

I think we are going to have to find a different way of doing that...

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2011-06-04 16:33:38 Re: reducing the overhead of frequent table locks - now, with WIP patch
Previous Message Heikki Linnakangas 2011-06-04 16:20:52 Re: SIREAD lock versus ACCESS EXCLUSIVE lock