Re: plperl fails with perl 5.14.0

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org, marti(at)juffo(dot)org
Subject: Re: plperl fails with perl 5.14.0
Date: 2011-06-04 17:05:13
Message-ID: 4DEA65C9.90507@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


There was some discussion on this about 6 weeks ago, at which time 5.14
wasn't released, so I didn't want to apply the patch then.

I'll look at applying the fix now.

cheers

andrew

On 06/04/2011 12:30 PM, Tom Lane wrote:
> 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
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2011-06-04 17:31:17 Re: plperl fails with perl 5.14.0
Previous Message Kevin Grittner 2011-06-04 16:56:08 Re: SIREAD lock versus ACCESS EXCLUSIVE lock