> This is the only problem on python side of things to make extensions
> buildable on windows x64 (all the other problems I have encountered so
> far to make numpy build with mingw-w64 are numpy's or mingw-w64).
Thanks!
Martin
--
http://mail.python.org/mailman/listinfo/python-list
On Fri, Dec 19, 2008 at 3:30 PM, "Martin v. Löwis" wrote:
>> - Any extension requires the MS_WIN64 to be defined, but this symbol
>> is only defined for MS compiler (in PC/pyport.h).
>
> Why do you say that? It is only defined when _WIN64 is defined; this
> has nothing to do with a MS compiler.
>
On Fri, Dec 19, 2008 at 3:30 PM, "Martin v. Löwis" wrote:
>
> It's a mistake if libpython26.a gets included in the Win64 installer
> at all; this library is only provided for 32-bit systems. My copy of
> mingw doesn't support Win64 at all.
Please ignore that last point: it looks like it is gener
> - Any extension requires the MS_WIN64 to be defined, but this symbol
> is only defined for MS compiler (in PC/pyport.h).
Why do you say that? It is only defined when _WIN64 is defined; this
has nothing to do with a MS compiler.
> Shouldn't it be
> defined independantly of the compiler ?
You m
Hi,
I want to build python extensions with mingw-w64 on windows 64 bits. I
found some problems which I think are python bugs/deficiencies, but
would like a confirmation:
- Any extension requires the MS_WIN64 to be defined, but this symbol
is only defined for MS compiler (in PC/pyport.h). Shouldn
