2011/5/10 Tom Tromey <[email protected]>: >>>>>> "Ruben" == Ruben Van Boxem <[email protected]> writes: > > Ruben> Ah, I didn't know this, that's indeed very handy, but the two > Ruben> occurrences in my patch are actually still a call to Py_InitModule > Ruben> without the "4". Then that probably needs to be patched instead? > > No, there's a later define for that in modsupport.h: > > #define Py_InitModule(name, methods) \ > Py_InitModule4(name, methods, (char *)NULL, (PyObject *)NULL, \ > PYTHON_API_VERSION) > > I think the thing to do is track down why the Python headers are picking > the wrong function name for you. > > Tom >
OK, found the problem. Apparantly the pyconfig.h header only defined MS_WIN* when _MSC_VER is defined, which is obviously not the case for mingw-w64. I guess people attempted fixing it here (http://bugs.python.org/issue4709), but the patch never landed. Sorry for the noise here. I'll just add "-DMS_WIN64" to the CFLAGS for GDB. Pretty lame of Python devs though, with all the work put into the tiny and overly correct patch. I'll ping them there and work around this locally. Thanks for the quick response here! Ruben ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
