From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Marco Atzeri <marco(dot)atzeri(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Subject: | Re: PostgreSQL 9.5 Alpha 1 build fail with perl 5.22 |
Date: | 2015-07-13 21:18:47 |
Message-ID: | 15818.1436822327@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-announce pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 07/13/2015 11:53 AM, Marco Atzeri wrote:
>> On 7/13/2015 5:36 PM, Andrew Dunstan wrote:
>>> hstore_plpython.o: In function `hstore_to_plpython':
>>> /home/andrew/bf64/root/HEAD/pgsql/contrib/hstore_plpython/hstore_plpython.c:35:
>>> undefined reference to `PLyUnicode_FromStringAndSize'
> No this doesn't seem to be the problem. For some reason it's apparently
> not finding the symbol in plpython3.dll, where it should definitely
> exist, unless I'm completely off base. So I'm rather confused.
Could hstore_plpython and plpython somehow have been built with different
ideas about PY_MAJOR_VERSION? PLyUnicode_FromStringAndSize is
conditionally compiled, and the reference to it from hstore_plpython
depends on a conditionally-defined macro, and this error would make plenty
of sense if those conditions somehow diverged. So I'd look for instance
at whether identical -I paths were used in both parts of the build.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2015-07-13 22:19:49 | Re: PostgreSQL 9.5 Alpha 1 build fail with perl 5.22 |
Previous Message | Andrew Dunstan | 2015-07-13 21:04:02 | Re: PostgreSQL 9.5 Alpha 1 build fail with perl 5.22 |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2015-07-13 22:19:49 | Re: PostgreSQL 9.5 Alpha 1 build fail with perl 5.22 |
Previous Message | Andres Freund | 2015-07-13 21:16:51 | Re: [DESIGN] Incremental checksums |