2009/4/25 patrick flaherty p...@well.com:
Starting with this:
http://oldwiki.mingw.org/index.php/Python%20extensions
I believe the problem to be in distutils. Something needs to be
modified to accommodate x86_64-pc-mingw32-gcc.
So far, from distutils, I've been through msvccompiler.py,
But how does one check an image to directly to see if it's compiled 32 or 64
bits?
objdump -h for instance. An objdump built for just 32-bit mingw won't
even recognize a 64-bit binary. An objdump built for 64-bit mingw will
tell you that a 32-bit binary is file format pei-i386 and a 64-bit
is
Hello Patrick,
2009/4/24 patrick flaherty p...@well.com:
Hi,
I successfully built the Sourceforge pyOpenSSL project with mingw32.
But I'm on a 64-bit machine and have had problems with loading the project's
DLLs at runtime (on a 32 bit machine loading the DLLs works fine) and when I
found
Thanx Tor - did as you instructed.
The hello.exe compiled with x86_64-pc-mingw32-gcc is about 10X the size
of the one compiled with simply gcc which would seem to indicate that
the former is a 64 bit image and the latter 32.
But how does one check an image to directly to see if it's
Hi,
I successfully built the Sourceforge pyOpenSSL project with mingw32.
But I'm on a 64-bit machine and have had problems with loading the
project's DLLs at runtime (on a 32 bit machine loading the DLLs works
fine) and when I found mingw-64 on sourceforge thought I'd give it a try
and see
