Re: Debian build problem with 1.4.1

2004-08-20 Thread Otis Gospodnetic
Hello Jeff, I don't have Debian to try this out, and this is going to be a stupid question and suggestion, but where/how is the CLASSPATH set? Are any of those commands actually using Lucene's build.xml? I'm asking, because it looks like your compiler is not finding Reader and IOException

Re: Debian build problem with 1.4.1

2004-08-20 Thread Jeff Breidenbach
Hi Otis, I'm asking, because it looks like your compiler is not finding Reader and IOException classes, both of which are in java.io.* package, which I see imported in StandardTokenizer.java as 'import java.io.*;'. In my copy of StandardTokenizer.java, there is no 'import java.io.*;' (and in

Re: Debian build problem with 1.4.1

2004-08-20 Thread Erik Hatcher
On Aug 20, 2004, at 11:12 AM, Jeff Breidenbach wrote: Hi Otis, I'm asking, because it looks like your compiler is not finding Reader and IOException classes, both of which are in java.io.* package, which I see imported in StandardTokenizer.java as 'import java.io.*;'. In my copy of

Re: Debian build problem with 1.4.1

2004-08-20 Thread Jeff Breidenbach
I don't understand this. StandardTokenizer.java hasn't changed since last year. I have packaged Lucene such that 'ant javacc' is called at package build time. I now see the problem - 'import java.io.*;' has been removed from StandardTokenizer.jj in Lucene 1.4.1. When I put that line back in,

Re: Debian build problem with 1.4.1

2004-08-20 Thread Jeff Breidenbach
Ok, Lucene 1.4.1 has been uploaded to Debian. Hopefully it will have enough time to percolate before the sarge release. Now that that is taken care of, I'm curious about the status of gcj compilation. Packaging Lucene as a native library might be useful for projects such as PyLucene, and it is

Re: Debian build problem with 1.4.1

2004-08-20 Thread Erik Hatcher
On Aug 20, 2004, at 12:36 PM, Jeff Breidenbach wrote: I don't understand this. StandardTokenizer.java hasn't changed since last year. I have packaged Lucene such that 'ant javacc' is called at package build time. I now see the problem - 'import java.io.*;' has been removed from

Re: Debian build problem with 1.4.1

2004-08-20 Thread Doug Cutting
I can successfully use gcc 3.4.0 with Lucene as follows: ant jar jar-demo gcj -O3 build/lucene-1.5-rc1-dev.jar build/lucene-demos-1.5-rc1-dev.jar -o indexer --main=org.apache.lucene.demo.IndexHTML ./indexer -create docs It runs pretty snappy too! However I don't know if there's much milage in

Re: Debian build problem with 1.4.1

2004-08-20 Thread Jeff Breidenbach
It's easy enough for folks to compile Lucene this way I'm having trouble, warnings and error messages appended. This is for Lucene 1.4.1. One of the few Debian specific changes was to call the jarball 1.4 instead of the default 1.5-rc1-dev designation in build.xml. rode:~ gcj --version gcj

Debian build problem with 1.4.1

2004-08-19 Thread Jeff Breidenbach
Hi all, I am the Debian package maintainer for Lucene, and I'm having build problems with 1.4.1. We are very close to a major Debian release (code named 'sarge'), and the window for changes is very small. Can someone please help me in the next day or two, otherwise Debian stable will ship Lucene