Re: [HACKERS] PL/Perl build problem: error: ‘OP_SETSTATE’ undeclared
| От | Alex Hunsaker |
|---|---|
| Тема | Re: [HACKERS] PL/Perl build problem: error: ‘OP_SETSTATE’ undeclared |
| Дата | |
| Msg-id | CAFaPBrSQ_uQLj2qHYS4i3NbPf2dS8PRYzHh9Gz=4O=RRiH28gA@mail.gmail.com обсуждение исходный текст |
| Ответ на | PL/Perl build problem: error:‘OP_SETSTATE’ undeclared (Peter Eisentraut <peter_e@gmx.net>) |
| Ответы |
Re: Re: [HACKERS] PL/Perl build problem: error:‘OP_SETSTATE’ undeclared
|
| Список | pgsql-hackers |
On Sun, Aug 12, 2012 at 9:57 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
It appears that a recent Perl version (I have 5.14.2) has eliminated
OP_SETSTATE, which causes the current PostgreSQL build to fail:
plperl.c: In function ‘_PG_init’:
plperl.c:442:5645: error: ‘OP_SETSTATE’ undeclared (first use in this function)
plperl.c:442:5645: note: each undeclared identifier is reported only once for each function it appears in
Hrm, Thats strange, PLPERL_SET_OPMASK() is generated by plperl_opmask.pl-- that should use whatever OP's your current perl has defined (They come from the "use Opcode" at the top and unless you somehow installed a different Opcode module than what your perl has...).
Im running a non threaded 5.16.0 and I don't see OP_SETSTATE anywhere:
$ pwd
/home/alex/src/postgresql/src/pl/plperl
$ grep -RI 'OP_SETSTATE' *
$
I know i've used 5.14 in the past successfully. Wat happens if you regenerate plperl_opmask.h? (rm plperl_opmask.h && make)
В списке pgsql-hackers по дате отправления: