On Nov 30, 2010, at 13:13, Bill Janssen wrote:
Andi Vajda wrote:
So you're mixing three compiler runtimes ? (7.1, 9.0, mingw-gcc)
Yes, that's right. Although the promise of MinGW is that they build
MSVC-compatible programs which link with the standard MSVC libraries.
In fact, when you r
Andi Vajda wrote:
> So you're mixing three compiler runtimes ? (7.1, 9.0, mingw-gcc)
Yes, that's right. Although the promise of MinGW is that they build
MSVC-compatible programs which link with the standard MSVC libraries.
In fact, when you run the Windows equivalent of ldd on _jcc.pyd, you se
On Tue, 30 Nov 2010, Bill Janssen wrote:
Andi Vajda wrote:
Try without --find-jvm-dll and setting the Path in the shell first.
Yes, I've tried it both ways -- same problem.
"the Web" seems to indicate that this problem comes from mixing "malloc"
and "free" calls from two different libc's.
On Tue, 30 Nov 2010, Bill Janssen wrote:
Andi Vajda wrote:
Also, note how version 9 of msvcrt.dll is on the stack. Is that what
you'd expect from your mingw build ?
Yes, here's the somewhat elided link line:
C:\MinGW\bin\g++.exe -mno-cygwin -shared -s
build\temp.win32-2.7\Release\jcc\sou
Andi Vajda wrote:
> Try without --find-jvm-dll and setting the Path in the shell first.
Yes, I've tried it both ways -- same problem.
"the Web" seems to indicate that this problem comes from mixing "malloc"
and "free" calls from two different libc's.
Bill
