Jan Harkes added the comment:
@Carl.Kleffner: that is an interesting message but it discusses using
binutils(/mingw?) generated import libraries with the MS linker.
This bugreport was about two 64-bit objects that were accidentally included in
an otherwise 32-bit library and it has been
Jan Harkes added the comment:
Just noticed in Matthew Barnett's comment that he has an additional
"--as-flags=--32" argument.
x86_64-w64-mingw32-dlltool --as-flags=--32 --dllname python27.dll --def
mingwlib.def --output-lib win32\libpython27.a -m i386
Creates a correct libp
Jan Harkes added the comment:
The Python-2.7.9 version of the Windows-x86 MSI installed version works fine
with the 32-bit mingw. In fact I rolled back to that release and built my code
successfully.
Somehow the fix for https://bugs.python.org/issue23199 must have broken the
32-bit
New submission from Jan Harkes:
mingw32 fails to link with libpython27.a fails with the following error
/cygdrive/C/Python27/libs/libpython27.a: error adding symbols: File format not
recognized
extracting all the objects from libpython27.a and checking them with objdump
shows that two
