I settled for the "fix" of using mingw.org gcc 4.6.2 32bit but don't understand
why it works since the 4.6.2 .pyd's still have deps on msvcr90.dll and msvcrt.dll...need
to try again with a custom spec to force everything to msvcr90.dll and try with
http://sourceforge.net/projects/mingwbuilds/files/host-windows/releases/4.7.2/
There are ABI changes between mingw.org's 4.6.2 and 4.7 that require
all libraries to use one or the other. I don't know if nixMan's
releases would have the same issue but if it were me I would be sure
to rebuild all libraries and modules with the same compiler. You are
likely to have issues between mingw.org's gcc built libraries and
other's releases of gcc.
Ah, good to know. My goal is to use the official Python binary (VC built?) and
use mingw-w64 4.7.2 (Ruben or nixMan's) to build the modules, and not have to
build everything with the same toolchain.
We're on the same boat then. I cannot got 32bit as Jon did due to the
4GB address-space restriction. The official python build is MSVC2008
(http://stackoverflow.com/questions/2676763/what-version-of-visual-studio-is-this-python-compiled-with).
Please report any progress you have here or, if you think it is not
appropriate, privately, I will be happy to hear about it.
If I can't get any further, I will play with Python built with MinGW
(which is problematic in itself, though...).
Cheers, Vaclav
------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
