Benjamin Gilbert added the comment: Steve, I don't think that's the right characterization of this bug. Putting 64-bit .o files in a 32-bit import library seems wrong for both MinGW and MinGW-w64.
msg244874 says that if you use the dlltool from the *32-bit* MinGW-w64 to build the 32-bit import library, the problem does not occur. msg244875 says that you can even use the 64-bit MinGW-w64 dlltool by passing one additional command-line option. Why not pursue one of those solutions? ---------- title: libpython.a does not work for all MinGW forks -> libpython27.a in python-2.7.10 i386 (windows msi release) contains 64-bit objects _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24385> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
