problem building python 3.5 extensions for windows

Robin Becker robin at reportlab.com
Wed Sep 23 12:20:06 CEST 2015


On 22/09/2015 22:37, cjgohlke at gmail.com wrote:
> On Tuesday, September 22, 2015 at 1:49:16 PM UTC-7, Terry Reedy wrote:
>> On 9/22/2015 9:35 AM, Robin Becker wrote:
>>> On 22/09/2015 11:14, Robin Becker wrote:
>>>> On 22/09/2015 01:36, CG wrote:
>>> .........t
>>>>> <http://bugs.python.org/issue24872#msg249589>.
>>>>>
>>>> Thanks for the pointer Christoph.
>>>>
>>>> I certainly didn't let it run for 30 minutes. When I build with 2.7,
>>>> 3.3 or 3.4
>>>> the whole build including reportlab stuff is over in a couple of
>>>> minutes. I will
>>>> try again, but a linker that takes 30 minutes to create an extension
>>>> that ends
>>>> up 204Kb long has to be seriously broken. Is it trying to hard? Most
>>>> of the code
>>>> size is in arrays for code points etc etc.
>>>
>>> I timed my builds of pyRXPU for x86 + amd64; these are on a core i5-3470
>>> @ 3.20Ghz with 4Gb memory.
>>>
>>> python 3.4   1 minute  14 seconds
>>> python 3.5  52 minutes 50 seconds
>>>
>>> so with VS2015 it will now take me an hour to make and test any changes
>>> to this extension. I don't see how the issue can be considered closed.
>>> VS2015 is clearly not the way forward for any reasonable development
>>> process.
>>
>> I think you should add the above to the issue.
>>
>> --
>> Terry Jan Reedy
>
> It's a compiler bug. To work around, disable compiler optimizations, i.e. set `extra_compile_args=['/Od']` in setup.py.
>
> --
> Christoph
>
Thanks Christoph, I guessed it must be something like that. I suppose it's 
trying desperately to place small chunks of encoding tables or something.

-- 
Robin Becker



More information about the Python-list mailing list