Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-07 Thread Earnie Boyd
On Wed, Nov 7, 2012 at 6:33 AM, Václav Šmilauer wrote: > >>> Just for the heck of it, I changed >>> Python27/lib/distutils/cygwincompiler.py to return "msvcrt" instead of >>> "msvcr90". It works. >>> >>> My question is: do we really need to link our modules to msvcr*, if >>> python.dll (which we l

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-07 Thread Ruben Van Boxem
2012/11/7 Václav Šmilauer > > >> Just for the heck of it, I changed > >> Python27/lib/distutils/cygwincompiler.py to return "msvcrt" instead of > >> "msvcr90". It works. > >> > >> My question is: do we really need to link our modules to msvcr*, if > >> python.dll (which we link already when build

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-07 Thread Václav Šmilauer
>> Just for the heck of it, I changed >> Python27/lib/distutils/cygwincompiler.py to return "msvcrt" instead of >> "msvcr90". It works. >> >> My question is: do we really need to link our modules to msvcr*, if >> python.dll (which we link already when building modules) links to msvcrt >> itself? I

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-06 Thread Earnie Boyd
On Tue, Nov 6, 2012 at 5:04 AM, Václav Šmilauer wrote: > >> I'm hoping my load fail (and the OP's) turns out to be the issue of >> modules linking against two different CRT versions. PeStudio tells me >> my msvcrt.dll linked .pyd's try to use _errno, __dllonexit, fflush, >> free, malloc, and strcm

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-06 Thread Václav Šmilauer
>> I'm hoping my load fail (and the OP's) turns out to be the issue of >> modules linking against two different CRT versions. PeStudio tells me >> my msvcrt.dll linked .pyd's try to use _errno, __dllonexit, fflush, >> free, malloc, and strcmp from msvcr90.dll. > Just for the heck of it, I changed

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-06 Thread Václav Šmilauer
> I'm hoping my load fail (and the OP's) turns out to be the issue of > modules linking against two different CRT versions. PeStudio tells me > my msvcrt.dll linked .pyd's try to use _errno, __dllonexit, fflush, > free, malloc, and strcmp from msvcr90.dll. Just for the heck of it, I changed Py

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-05 Thread Алексей Павлов
Hi! For building python with mingw you need some patches) You can find them on https://github.com/niXman/mingw-builds/tree/master/patches/Python-2.7.3. 2012/11/5 Václav Šmilauer > > Hi, Vaclav! > Can you try to build python module with this > toolchain

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-05 Thread Václav Šmilauer
I settled for the "fix" of using mingw.org gcc 4.6.2 32bit but don't understand why it works since the 4.6.2 .pyd's still have deps on msvcr90.dll and msvcrt.dll...need to try again with a custom spec to force everything to msvcr90.dll and try with http://sourceforge.net/projects/mingwbuilds/fi

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-05 Thread Václav Šmilauer
>>> 3c) Move 32bit libs out of the way >>> (http://gcc.gnu.org/ml/gcc-help/2012-07/msg00060.html suggests to use >>> -static-libstdc++, but it is not recognized by gcc 4.7); I don't compile >>> 32bit programs, so not having 32bit versions is fine for me: >>> >>> cd /c/MinGW64/bin >>> m

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-05 Thread Václav Šmilauer
>> 2a) [!!!] run gendef and dlltool on python27.dll >> (http://stackoverflow.com/q/11182765/761090) to be able to -lpython27. > How is that suspicious? Having no experience here, I thought it was some hack. You seem to suggest this is the standard way. Good :-) >> 3a) Copy msvcr90.dll (c:\Windows

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-05 Thread Václav Šmilauer
Hi, Vaclav! Can you try to build python module with this toolchain ? There are Python-2.7.3 in subdirectory "opt" compiled with this toolchain. Hi Alex, thanks for your suggestion, I would like to first try with

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-02 Thread Jon
On Fri, 2 Nov 2012 15:20:10 -0400 Earnie Boyd wrote: > On Fri, Nov 2, 2012 at 3:01 PM, Jon wrote: > > > > I settled for the "fix" of using mingw.org gcc 4.6.2 32bit but don't > > understand why it works since the 4.6.2 .pyd's still have deps on > > msvcr90.dll and msvcrt.dll...need to try again

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-02 Thread Earnie Boyd
On Fri, Nov 2, 2012 at 3:01 PM, Jon wrote: > > I settled for the "fix" of using mingw.org gcc 4.6.2 32bit but don't > understand why it works since the 4.6.2 .pyd's still have deps on msvcr90.dll > and msvcrt.dll...need to try again with a custom spec to force everything to > msvcr90.dll and try

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-02 Thread Jon
> I am trying to build compiled python modules, which use some compiled > libraries (boost, in particular). The system is Windows 7 64bit Pro. One > of them (http://pypi.python.org/pypi/minieigen/0.3-4) works fine, > another one (source not publicly available yet) does not. FYI, I had a simil

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-01 Thread John E. / TDM
On 11/1/2012 4:11 PM, JonY wrote: > On 11/1/2012 22:13, Václav Šmilauer wrote: >> 3c) Move 32bit libs out of the way >> (http://gcc.gnu.org/ml/gcc-help/2012-07/msg00060.html suggests to use >> -static-libstdc++, but it is not recognized by gcc 4.7); I don't compile >> 32bit programs, so not having

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-01 Thread JonY
On 11/1/2012 22:13, Václav Šmilauer wrote: > Hi everybody, > > I am fairly new to MinGW64 (and to windows) and this is my first post to > the list. I would like to thank to the authors of and contributors to > mingw64 in the first place. > > I am trying to build compiled python modules, which use

Re: [Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-01 Thread Алексей Павлов
Hi, Vaclav! Can you try to build python module with this toolchain? There are Python-2.7.3 in subdirectory "opt" compiled with this toolchain.

[Mingw-w64-public] Error building python extension (DLL load failed: invalid access to memory location)

2012-11-01 Thread Václav Šmilauer
Hi everybody, I am fairly new to MinGW64 (and to windows) and this is my first post to the list. I would like to thank to the authors of and contributors to mingw64 in the first place. I am trying to build compiled python modules, which use some compiled libraries (boost, in particular). The