On Wed, Apr 29, 2015 at 5:15 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On 4/28/15 4:10 PM, Andrew Dunstan wrote:
>>> Do we actually have a Windows machine building with Python3?
>>
>>
>> The answer seems to be "probably not". When I tried enabling this with
>> bowerbird I got a ton of errors like these:
>>
>> plpy_cursorobject.obj : error LNK2001: unresolved external symbol
>> PyObject_SelfIter [C:\prog\bf\root\HEAD\pgsql\plpython3.vcxproj]
>> plpy_cursorobject.obj : error LNK2019: unresolved external symbol
>> __imp_PyType_Ready referenced in function PLy_cursor_init_type
>> [C:\prog\bf\root\HEAD\pgsql\plpython3.vcxproj]
>>
>>
>> Something else to fix I guess.
>
> I think at least at one point the community Windows binaries built by
> EnterpriseDB were built against Python 3 (which upset some users). But
> they might not be using the msvc toolchain.
Er, aren't you simply trying to link with 32b libraries while building
in a 64b environment? I am able to make the build work with python 3.
--
Michael