Building on Mingw64

Daniel Holden theonlydancingbanana@hotmail.com
Fri Nov 9 11:57:00 GMT 2012


Hi all,

I'm having a little trouble building libffi on Windows 7 64 bit using 
Mingw64 (http://mingw-w64.sourceforge.net/).

Here is the error message on compile:

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I. -I../include 
-Iinclude -I..
src -DFFI_BUILDING -I. -I../include -Iinclude -I../src -DFFI_BUILDING -g 
-MT sr
/x86/win32.lo -MD -MP -MF src/x86/.deps/win32.Tpo -c ../src/x86/win32.S  
-DDLL_
XPORT -DPIC -o src/x86/.libs/win32.o
../src/x86/win32.S: Assembler messages:
../src/x86/win32.S:486: Error: invalid instruction suffix for `push'
../src/x86/win32.S:497: Error: invalid instruction suffix for `push'
../src/x86/win32.S:498: Error: invalid instruction suffix for `push'
../src/x86/win32.S:643: Error: invalid instruction suffix for `pop'
../src/x86/win32.S:652: Error: invalid instruction suffix for `push'
../src/x86/win32.S:669: Error: invalid instruction suffix for `push'
../src/x86/win32.S:768: Error: invalid instruction suffix for `pop'
../src/x86/win32.S:780: Error: invalid instruction suffix for `pop'
../src/x86/win32.S:797: Error: invalid instruction suffix for `push'
../src/x86/win32.S:799: Error: invalid instruction suffix for `push'
../src/x86/win32.S:814: Error: invalid instruction suffix for `push'
../src/x86/win32.S:818: Error: invalid instruction suffix for `push'
../src/x86/win32.S:918: Error: invalid instruction suffix for `pop'
../src/x86/win32.S:919: Error: invalid instruction suffix for `pop'
../src/x86/win32.S:934: Error: invalid instruction suffix for `push'
../src/x86/win32.S:1032: Error: invalid instruction suffix for `pop'
make[3]: *** [src/x86/win32.lo] Error 1

I know very little about assembly but this looks like a 32/64 bit issue. 
Is MinGW64 supported as a compiler?

The reason I ask is that I was getting some issues when I was using 
Pyton ctypes and trying to call particular functions in a C library 
compiled using MinGW64. The details I outlined in this stack overflow 
question:

http://stackoverflow.com/questions/13275211/python-ctypes-stack-corruption

I was going to test to see if just using libffi also gives any issues.

Thanks,

Dan



More information about the Libffi-discuss mailing list