Hi tsuraan. I am not really sure what is going on if 1.0.1 will work while 1.9.1 and 2.0.0 will not. Should they not all fail if this were the case? For me this is more about getting a newer release of PyLucene working since 1.0.1 seemed to work fine on FreeBSD 4.10 with gcc41 for me and also reported to work on FreeBSD 4.11 fine by another person.

I've never used or looked at 1.0.1, so I don't know what changes exist between then and 1.9.1. I've also never used the 4.x series of FreeBSD, so I don't know anything about that, either :)

I can give this a try for sure. gcc34 is available in ports collection. I think gcj was only set up for 4.1 ports. I have been commenting out the

WITHOUT_JAVA = yes

in the port Makefile for gcc41 to build with java

Did you keep any notes for your gcc34 build that you could share. Do you a newer PyLucene version than 1.0.1 running on FreeBSD 5.x or 6.x? Many thanks

I built the version of gcc recommended in the Makefile (3.4.5, I think) from the gcc.gnu.org source package, installing it to /opt. I didn't apply any patches, and my only configure options were prefix=/opt and enable-languages="c,c++,java". That worked for 1.9.1, and I believe it also works for 2.0. I can't find the machine that I used to build it right now; dhcp seems to have changed its IP address. When I find the build machine, I'll see what the exact gcc version is, but I know I didn't do anything special to make it work.

_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev

Reply via email to