[Wine] [Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now

Luke Kenneth Casson Leighton lkcl at lkcl.net
Wed Jan 21 05:08:23 CST 2009

> It only becomes a problem when someone wants to both support Windows
> users of their extension modules with pre-built binaries, but *also*
> doesn't want to set up the appropriate environment for building such
> binaries (currently a minimum bar of Visual Studio Express on a Windows
> VM instance).

ok - fortunately, thanks to dan kegel for pointing me in the right
direction of "winetricks vcrun2005p1" i was able to get a successful
build using Microsoft.VC8.CRT assemblies.

i say "successful" because Parser/pgen.exe was built and ran, and
libpython2.5.dll.a was also successfully built, as was python.exe
successfully built.

the problem _now_ to overcome is that the bloody libmsvcrt80.a has the
wrong definitions, for a 32-bit build!  it has functions like _fstat
instead of _fstat32 and so on.

if this was a 64-bit version of wine i was using mingw32 under, i
would not have encountered this issue.

amazingly, however, someone _else_ who kindly tried out compiling
python2.5 with mingw and msvcr80, native on win32, reported that it
was a complete success! as in, "successful build, successful install,
successful run of tests, only 4 failed regression tests".  i am
utterly mystified as to how that happened.

next task: beat the crap out of libmsvcr80.a and /mingw/include/*.h,
repeat until success.


More information about the wine-users mailing list