Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-12-01 Thread Bill Janssen
Andi Vajda wrote: > I believe MSVC 2008 == 9.0 but I could be wrong. I also seem to recall > that Python 2.7 requires that version. So you should also try Python > 2.6 on Win 7. I asked about this on the mingw list, with the following result: Charles Wilson wrote: > The official python.org wi

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-30 Thread Andi Vajda
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

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-30 Thread Bill Janssen
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

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-30 Thread Andi Vajda
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.

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-30 Thread Andi Vajda
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

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-30 Thread Bill Janssen
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

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-29 Thread Andi Vajda
On Nov 29, 2010, at 18:40, Bill Janssen wrote: Bill Janssen wrote: Andi Vajda wrote: I just tried this myself By "this", do you mean 64-bit Windows 7, or Python 2.7? Both. 64 bit Windows 7, with Python 2.7 and Java 1.6.0_22 both 32-bit. OK, I'll try it again on Win 7. I'll use a c

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-29 Thread Andi Vajda
On Nov 29, 2010, at 18:40, Bill Janssen wrote: Bill Janssen wrote: Andi Vajda wrote: I just tried this myself By "this", do you mean 64-bit Windows 7, or Python 2.7? Both. 64 bit Windows 7, with Python 2.7 and Java 1.6.0_22 both 32-bit. OK, I'll try it again on Win 7. I'll use a c

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-29 Thread Bill Janssen
Bill Janssen wrote: > Andi Vajda wrote: > > > I just tried this myself > > >>> > > >>> By "this", do you mean 64-bit Windows 7, or Python 2.7? > > >> > > >> Both. 64 bit Windows 7, with Python 2.7 and Java 1.6.0_22 both 32-bit. > > > OK, I'll try it again on Win 7. I'll use a checkout of

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-29 Thread Andi Vajda
On Nov 29, 2010, at 18:08, Bill Janssen wrote: Andi Vajda wrote: I just tried this myself By "this", do you mean 64-bit Windows 7, or Python 2.7? Both. 64 bit Windows 7, with Python 2.7 and Java 1.6.0_22 both 32- bit. OK, I'll try it again on Win 7. I'll use a checkout of the PyLucen

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-29 Thread Bill Janssen
Andi Vajda wrote: > I just tried this myself > >>> > >>> By "this", do you mean 64-bit Windows 7, or Python 2.7? > >> > >> Both. 64 bit Windows 7, with Python 2.7 and Java 1.6.0_22 both 32-bit. > > OK, I'll try it again on Win 7. I'll use a checkout of the PyLucene > > trunk instead of a pa

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-29 Thread Bill Janssen
Andi Vajda wrote: > > On Nov 29, 2010, at 9:45, Bill Janssen wrote: > > > Andi Vajda wrote: > > > >> I just tried this myself > > > > By "this", do you mean 64-bit Windows 7, or Python 2.7? > > Both. 64 bit Windows 7, with Python 2.7 and Java 1.6.0_22 both 32-bit. > > > > >> and it seems th

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-29 Thread Andi Vajda
On Nov 29, 2010, at 9:45, Bill Janssen wrote: Andi Vajda wrote: I just tried this myself By "this", do you mean 64-bit Windows 7, or Python 2.7? Both. 64 bit Windows 7, with Python 2.7 and Java 1.6.0_22 both 32-bit. and it seems that with Python 2.7 __name__ is never equal to '__mai

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-29 Thread Bill Janssen
Andi Vajda wrote: > I just tried this myself By "this", do you mean 64-bit Windows 7, or Python 2.7? > and it seems that with Python 2.7 __name__ is > never equal to '__main__' in jcc's __init__.py. So, jcc.__main__ is > never imported implicitely from __init__.py and hence --find-jvm-dll > is

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-23 Thread Roman Chyla
On Mon, Nov 22, 2010 at 9:45 PM, Bill Janssen wrote: > Roman Chyla wrote: > >> I had similar/same issue on win xp, it was the space in the java path, >> but i can't recall details. What happens if you change config.py to? >> C:\\Program\ Files\ (x86)\\Java\\jdk1.6.0_22\\lib > > Wouldn't that eval

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-22 Thread Bill Janssen
Bill Janssen wrote: > Using depends.exe on _jcc.pyd says that the missing file is > Python27.dll, which seems odd. Where should I find that? And there is a python27.dll in C:\Windows\system32\. So, not sure what the problem is. Bill > > Bill > > > > > roman > > > > On Mon, Nov 22, 2010 a

Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

2010-11-22 Thread Bill Janssen
Roman Chyla wrote: > I had similar/same issue on win xp, it was the space in the java path, > but i can't recall details. What happens if you change config.py to? > C:\\Program\ Files\ (x86)\\Java\\jdk1.6.0_22\\lib Wouldn't that eval to the same Python string? I tried quoting all the spaces in