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 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
Regards
David
[EMAIL PROTECTED] wrote:
Hmm. Went back to my FreeBSD-4.10 installation and tried installing
1.9.1 and ran into the same trouble. I'll try 1.0.1 on FreeBSD-6. I
would be willing to bet it will work but this does not appear so great
for the two newer releases :-(
When I was trying to get things running under FreeBSD and gcc-4.x, I had
the following conversation with the gcj devs (link to my initial
posting): http://gcc.gnu.org/ml/java/2006-02/msg00004.html . It looks
like exception handling is hosed under FreeBSD and gcc-4.x, so maybe
that's giving you trouble. I had aborts rather than segmentation
faults, but the moral of the story seems to be that you really want to
use gcc-3.4.x and not the 4 series.
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
