clucene-developers — CLucene development-related discussion.

[CLucene-dev] Clucene web frontend

[Albert V. P. <av...@im...>]

Somebody has developed an Html front end for cLucene? This would be a 
very usefull demo to test the application.

Albert

[CLucene-dev] Clucene performance in front of Lucene

[Albert V. P. <av...@im...>]

I wanna know if someone has a performance benchmark between the C++ 
lucene version in front of the Java version (indexing speed, query 
speed, etc).
Thanks.

[CLucene-dev] Problems compiling cLucene with Dev-Cpp under Windows2000

[Albert V. P. <av...@im...>]

I'm trying to compile the cLucene project using Dev-cpp.
This is the compilation result:

Any help will be appreciate. Another question, is someone actually 
working with the cLucene project?, adding new features from Lucene, 
improving the performance, etc.

Compilador: Default compiler
Building Makefile: "C:\Avila\Projects\clucene\build\Dev-CPP\Makefile.win"
Ejecutando  make clean
rm -f tmp/Document.o tmp/Field.o tmp/StandardAnalyzer.o 
tmp/StandardFilter.o tmp/StandardTokenizer.o tmp/BitVector.o 
tmp/FastCharStream.o tmp/Misc.o tmp/Reader.o tmp/StringBuffer.o 
tmp/Arrays.o tmp/FieldInfos.o tmp/FieldsReader.o tmp/FieldsWriter.o 
tmp/IndexReader.o tmp/IndexWriter.o tmp/SegmentInfos.o 
tmp/SegmentMergeInfo.o tmp/SegmentMergeQueue.o tmp/SegmentMerger.o 
tmp/SegmentReader.o tmp/SegmentsReader.o tmp/SegmentTermDocs.o 
tmp/SegmentTermEnum.o tmp/SegmentTermPositions.o tmp/Term.o 
tmp/TermInfo.o tmp/TermInfosReader.o tmp/TermInfosWriter.o 
tmp/DocumentWriter.o tmp/QueryParser.o tmp/QueryParserBase.o 
tmp/QueryToken.o tmp/TokenList.o tmp/Lexer.o tmp/BooleanQuery.o 
tmp/BooleanScorer.o tmp/ExactPhraseScorer.o tmp/HitQueue.o tmp/Hits.o 
tmp/IndexSearcher.o tmp/PhrasePositions.o tmp/PhraseQuery.o 
tmp/PhraseScorer.o tmp/RangeQuery.o tmp/Similarity.o 
tmp/SloppyPhraseScorer.o tmp/TermQuery.o tmp/TermScorer.o tmp/TopDocs.o 
tmp/FSDirectory.o tmp/InputStream.o tmp/Lock.o tmp/OutputStream.o 
tmp/RAMDirectory.o tmp/test.o tmp/WildcardTermEnum.o tmp/DateFilter.o 
tmp/FilteredTermEnum.o tmp/MultiTermQuery.o tmp/PrefixQuery.o 
tmp/WildcardQuery.o tmp/DateField.o tmp/dirent.o tmp/StdHeader.o 
CLucene_private.res ../../bin/CLuceneGCC.exe

g++.exe -c ../../src/CLucene/document/Document.cpp -o tmp/Document.o 
-I"C:/Archivos de programa/Dev-Cpp/include/c++"  -I"C:/Archivos de 
programa/Dev-Cpp/include/c++/mingw32"  -I"C:/Archivos de 
programa/Dev-Cpp/include/c++/backward"  -I"C:/Archivos de 
programa/Dev-Cpp/include"  -I"../../src/" --define-macro 
COMPILER_MINGW32 --define-macro OS_WIN   -fexceptions -O3

In file included from ../../src/CLucene/document/Document.cpp:1:
../../src/CLucene/StdHeader.h:42:1: warning: "MAX_PATH" redefined
In file included from C:/Archivos de programa/Dev-Cpp/include/windows.h:48,
                 from C:/Archivos de 
programa/Dev-Cpp/include/c++/mingw32/bits/gthr-default.h:462,
                 from C:/Archivos de 
programa/Dev-Cpp/include/c++/mingw32/bits/gthr.h:98,
                 from C:/Archivos de 
programa/Dev-Cpp/include/c++/mingw32/bits/c++io.h:37,
                 from C:/Archivos de 
programa/Dev-Cpp/include/c++/bits/fpos.h:44,
                 from C:/Archivos de programa/Dev-Cpp/include/c++/iosfwd:46,
                 from C:/Archivos de 
programa/Dev-Cpp/include/c++/bits/stl_algobase.h:70,
                 from C:/Archivos de 
programa/Dev-Cpp/include/c++/bits/stl_tree.h:86,
                 from C:/Archivos de programa/Dev-Cpp/include/c++/map:66,
                 from ../../src/CLucene/StdHeader.h:12,
                 from ../../src/CLucene/document/Document.cpp:1:
C:/Archivos de programa/Dev-Cpp/include/windef.h:42:1: warning: this is 
the location of the previous definition
In file included from ../../src/CLucene/store/FSDirectory.h:33,
                 from ../../src/CLucene/util/Reader.h:5,
                 from ../../src/CLucene/document/Field.h:5,
                 from ../../src/CLucene/document/Document.h:5,
                 from ../../src/CLucene/document/Document.cpp:2:
../../src/CLucene/util/dirent.h:49: 'intptr_t' is used as a type, but is 
not defined as a type.

make.exe: *** [tmp/Document.o] Error 1

Ejecución Terminada

Re: [CLucene-dev] Distributed Indexing

[Doug C. <cu...@lu...>]

Albert Vila Puig wrote:
> For example, I can distribute half the data by document, having
> documents in one computer and other documents in another (that´s the
> simplest way, but you have to send a query to all the servers).

This is the preferred solution.  It scales very well.  Web search 
engines use it to search billions of documents.  Yes, you need to send 
each query to all of the servers, but on a 100Mbps network, this is not 
costly.

Doug

[CLucene-dev] Distributed Indexing

[Albert V. P. <av...@im...>]

Hi,

I have to develop a distributed search engine for my company. I’m very
interested with the Lucene index format, and I want to use it. The main
problem is how to distribute the index in the different machines.

The solution is not just copy the index, because I have to manage 50Gb
of data. I want to distribute the index in a more efficient way, I´ve
thought the best was doing it by document, by field or by term.

For example, I can distribute half the data by document, having
documents in one computer and other documents in another (that´s the
simplest way, but you have to send a query to all the servers).

Another way is distribute the index by field (I work only with XML data,
so a field will be a Xml element), having one field in one server, and
another one in other. This version seems more efficient because you only
have to send the query depending what field the user want to search.

The last solution is distribute the index by term. Then you only have to
send the query to those servers containing this term. Using the field
and term solution, I don’t want to distribute the documents with the
index (because on document can contain a lot of terms, and I don’t want
to distribute the same document in all the computers), just the
documentID, and have the pair <documentID, document> in another computer.

I’m planning to have an indexing server, which will be in charge of
indexing the data and then distribute it over the n backend servers
(depending if the distribution is per document, per field or per term;
the indexing server will have to look the lucene index and distribute
only the needed parts). Then, the search server will know these
distribution and will only send the queries to the appropriate servers.

I want a include replication in order to increase the fiability as well.

Any comments, suggestions and/or problems. Do you think It is a
realistic/good solution?

Thanks,

Albert

[CLucene-dev] Distributed Indexing

[Albert V. P. <av...@im...>]

Hi,

I have to develop a distributed search engine for my company. I’m very 
interested with the Lucene index format, and I want to use it. The main 
problem is how to distribute the index in the different machines.

The solution is not just copy the index, because I have to manage 50Gb 
of data. I want to distribute the index in a more efficient way, I´ve 
thought the best was doing it by document, by field or by term.

For example, I can distribute half the data by document, having 
documents in one computer and other documents in another (that´s the 
simplest way, but you have to send a query to all the servers).

Another way is distribute the index by field (I work only with XML data, 
so a field will be a Xml element), having one field in one server, and 
another one in other. This version seems more efficient because you only 
have to send the query depending what field the user want to search.

The last solution is distribute the index by term. Then you only have to 
send the query to those servers containing this term. Using the field 
and term solution, I don’t want to distribute the documents with the 
index (because on document can contain a lot of terms, and I don’t want 
to distribute the same document in all the computers), just the 
documentID, and have the pair <documentID, document> in another computer.

I’m planning to have an indexing server, which will be in charge of 
indexing the data and then distribute it over the n backend servers 
(depending if the distribution is per document, per field or per term; 
the indexing server will have to look the lucene index and distribute 
only the needed parts). Then, the search server will know these 
distribution and will only send the queries to the appropriate servers.

I want a include replication in order to increase the fiability as well.

Any comments, suggestions and/or problems. Do you think It is a 
realistic/good solution?

Thanks,

Albert

[CLucene-dev] Re: crash in current CVS CLucene

[<rg...@sd...>]

>>>>> "Rob" == Rob Ristroph <rg...@sd...> writes:
Rob> 
Rob> If you run the current CVS version of the demo on this set of
Rob> docs:
Rob> 
Rob> http://www.daviddlewis.com/resources/testcollections/reuters21578/
Rob> 
Rob> It will segfault.  Can anyone else confirm this so I know it is
Rob> not just my setup ?
Rob> 
Rob> It looks like some memory thing.  I ran it in gdb and it did not
Rob> crashing; crashing outside of gdb and not crashing in it is a
Rob> sign of weird memory problems, in my experience.  So I ran it
Rob> with valgrind, which listed some errors, which I am still working
Rob> on as I am not too experienced with valgrind (it crashed in
Rob> valgrind).
Rob> 
Rob> I will post more information soon, this weekend if not sooner.
Rob> 
Rob> --Rob

Please disregard this.  After beating my head on it for way too long,
I have discovered that when I recompile it goes away.  I suspect bad
memory in my computer produced a bad build.  This is because I have
had other problems generally associated with bad memory, such as gcc
internal errors.

I still have a different issue I'm working on though.  More about it
later.

--Rob

Re: [CLucene-dev] crash in current CVS CLucene

[<rg...@sd...>]

>>>>> "ben" == ben  <be...@vi...> writes:
ben> 
ben> Hi,
ben> I haven't run it over the documents you specified. But i suspect
ben> it's the non-ascii problem again. Can someone try building a
ben> unicode linux version?  I'm sure that will solve many problems.
ben> 
ben> Ben

I suspect that this particular crash isn't the ascii problem, but I'll
look into the unicode.

--Rob

Re: [CLucene-dev] DLL Test

[Eduardo M. <em...@ac...>]

> Thanks Eduardo,
>
> That was a bug. I have fixed it now, I will put it up in the next
> release.
>
> The reason was that Clucene caches the first 100 documents, then when
> the next 100 is required, it is re-queried. But the query was being
> destroyed after the initial query, so the second query would fail.

Great. I am glad I could help. I have just one suggestion. The DLL is not
usefull since all variables are global. I suggest to change it to have one
method to initialize the engine, returning a handle to the allocated
variables, and another one to destroy them. All others methods will need the
handle in order to access the engine. I can make the change myself but I
think more people would need such modification.

BTW, great work.

> If you want the fix sooner, please email me.

Thanks, I can wait. But I am not sure if my nails can. :-)

Eduardo Mauro

Re: [CLucene-dev] crash in current CVS CLucene

[<be...@vi...>]

Hi,

I haven't run it over the documents you specified. But i suspect it's the
non-ascii problem again. Can someone try building a unicode linux version?
I'm sure that will solve many problems.

Ben

>
> If you run the current CVS version of the demo on this set of docs:
>
> http://www.daviddlewis.com/resources/testcollections/reuters21578/
>
> It will segfault.  Can anyone else confirm this so I know it is not just
> my setup ?
>
> It looks like some memory thing.  I ran it in gdb and it did not
> crashing; crashing outside of gdb and not crashing in it is a sign of
> weird memory problems, in my experience.  So I ran it with valgrind,
> which listed some errors, which I am still working on as I am not too
> experienced with valgrind (it crashed in valgrind).
>
> I will post more information soon, this weekend if not sooner.
>
> --Rob
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> CLucene-developers mailing list
> CLu...@li...
> https://lists.sourceforge.net/lists/listinfo/clucene-developers

[CLucene-dev] crash in current CVS CLucene

[<rg...@sd...>]

If you run the current CVS version of the demo on this set of docs:

http://www.daviddlewis.com/resources/testcollections/reuters21578/

It will segfault.  Can anyone else confirm this so I know it is not
just my setup ?

It looks like some memory thing.  I ran it in gdb and it did not
crashing; crashing outside of gdb and not crashing in it is a sign of
weird memory problems, in my experience.  So I ran it with valgrind,
which listed some errors, which I am still working on as I am not too
experienced with valgrind (it crashed in valgrind).

I will post more information soon, this weekend if not sooner.

--Rob

Re: [CLucene-dev] OS X

[<rg...@sd...>]

>>>>> "Jesse" == Jesse Grosjean <jgr...@go...> writes:
Jesse> 
Jesse> Rob,
Jesse> anyway i've gotten future in the process, but am still not able
Jesse> to compile successfully. first i found that "libtoolize" has
Jesse> been renamed to "glibtoolize" on os x, so i ran
Jesse> 
Jesse> 	ln /usr/bin/glibtoolize /usr/local/bin/glibtoolize
Jesse> 
Jesse> and that seems to have fixed the "./bootstrap: libtoolize:
Jesse> command not found" problem. I've attached two terminal sessions
Jesse> bellow. The first is when i try to run bootstrap - configure -
Jesse> make all in a fresh version of clucene. if i run this sequence
Jesse> a second time it complains about a missing ltmain.sh in the
Jesse> bootstrap phase (it doesn't complete about this the first
Jesse> time). If i then copy this "ltmain.sh" file (i'm grabbing it
Jesse> from another library, metakit, that i've compiled on my
Jesse> computer) into the ./build folder where clucene is looking for
Jesse> it the compile process seems to get further. Though it still
Jesse> breaks pretty quickly.
Jesse> 
Jesse> let me know if you like temporary remote access to my os x
Jesse> machine i'd be happy to give it to you.
Jesse> 
Jesse> thanks,
Jesse> Jesse

I don't the time to take advantage of your offer right now, and I
expect to have an OS X machine of my own to experiment with soon.

I'm not sure what the problem is, but I think maybe you need to
install the latest libtool.  Maybe glibtool is something different.

--Rob

RE: [CLucene-dev] DLL Test

[Ben v. K. <s40...@st...>]

Thanks Eduardo,

That was a bug. I have fixed it now, I will put it up in the next
release. 

The reason was that Clucene caches the first 100 documents, then when
the next 100 is required, it is re-queried. But the query was being
destroyed after the initial query, so the second query would fail. 

If you want the fix sooner, please email me.
Thanks,
Ben

-----Original Message-----
From: clu...@li...
[mailto:clu...@li...] On Behalf Of
Eduardo Mauro
Sent: Tuesday, 16 September 2003 9:51 PM
To: clu...@li...
Subject: [CLucene-dev] DLL Test


I compiled DLL Test using Visual Studio 2003 and got strange results.
Take a look at query results:

94. note: This is a stored note., date: Tue Sep 16 08:17:23 2003 95.
note: This is a stored note., date: Tue Sep 16 08:17:23 2003 96. note:
This is a stored note., date: Tue Sep 16 08:17:23 2003 97. note: This is
a stored note., date: Tue Sep 16 08:17:23 2003 98. note: This is a
stored note., date: Tue Sep 16 08:17:23 2003 99. note: This is a stored
note., date: Tue Sep 16 08:17:23 2003 100. note: This is a stored note.,
date: Tue Sep 16 08:17:23 2003 101. note: (null), date: Wed Dec 31
22:00:00 1969 102. note: (null), date: Wed Dec 31 22:00:00 1969 103.
note: (null), date: Wed Dec 31 22:00:00 1969 104. note: (null), date:
Wed Dec 31 22:00:00 1969 105. note: (null), date: Wed Dec 31 22:00:00
1969 106. note: (null), date: Wed Dec 31 22:00:00 1969 107. note:
(null), date: Wed Dec 31 22:00:00 1969 108. note: (null), date: Wed Dec
31 22:00:00 1969 109. note: (null), date: Wed Dec 31 22:00:00 1969 110.
note: (null), date: Wed Dec 31 22:00:00 1969

I tried several times all with the same results. Examining the FTD file
seem it is ok. Also if I run the test several times in a sequences,
without erasing the directory, I always obtain the correct number of
hits but only the first 100 are correct.

Best regards,
Eduardo Mauro




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
CLucene-developers mailing list CLu...@li...
https://lists.sourceforge.net/lists/listinfo/clucene-developers

Re: [CLucene-dev] OS X

[Jesse G. <jgr...@go...>]

Rob,

> I think ltmain.sh is part of the libtool package, and the error
> message towards the end also mentions libtool.
>
> Can you run "libtool --version" at the command line and get a version
> number ?  I am compiling libtool with version 1.5a.  If you have no
> libtool, or if fink's libtool is old, you might have to download and
> install a newer libtool.

humm I certainly have a libtool command, but it doesn't take any 
version parameter.

> I regret that at the moment I do not have access to an OS X machine to
> test things on with you.  However, I might have access to one after
> the end of the month.
>
> If you are missing libtool or have an old version, that might explain
> things.

anyway i've gotten future in the process, but am still not able to 
compile successfully. first i found that "libtoolize" has been renamed 
to "glibtoolize" on os x, so i ran

	ln /usr/bin/glibtoolize /usr/local/bin/glibtoolize

and that seems to have fixed the "./bootstrap: libtoolize: command not 
found" problem. I've attached two terminal sessions bellow. The first 
is when i try to run bootstrap - configure - make all in a fresh 
version of clucene. if i run this sequence a second time it complains 
about a missing ltmain.sh in the bootstrap phase (it doesn't complete 
about this the first time). If i then copy this "ltmain.sh" file (i'm 
grabbing it from another library, metakit, that i've compiled on my 
computer) into the ./build folder where clucene is looking for it the 
compile process seems to get further. Though it still breaks pretty 
quickly.

let me know if you like temporary remote access to my os x machine i'd 
be happy to give it to you.

thanks,
Jesse

[Jesse-Grosjeans-Computer:~/Desktop/clucene-0.8.1-src] jessegrosjean% 
chmod 777 bootstrap
[Jesse-Grosjeans-Computer:~/Desktop/clucene-0.8.1-src] jessegrosjean% 
./bootstrap
+ libtoolize --force --copy --ltdl --automake
+ aclocal
+ autoconf
+ autoheader
+ automake -a --copy --foreign
configure.ac: installing `./build/gcc/config/install-sh'
configure.ac: installing `./build/gcc/config/mkinstalldirs'
configure.ac: installing `./build/gcc/config/missing'
Use of uninitialized value in concatenation (.) at /usr/bin/automake 
line 8393.
: installing `./build/gcc/config/config.guess'
Use of uninitialized value in concatenation (.) at /usr/bin/automake 
line 8393.
: installing `./build/gcc/config/config.sub'
aclocal.m4:846: required file `./build/gcc/config/ltmain.sh' not found
examples/demo/Makefile.am: installing `./build/gcc/config/depcomp'
automake: processing Makefiles another time to fix them up.
[Jesse-Grosjeans-Computer:~/Desktop/clucene-0.8.1-src] jessegrosjean% 
./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for gcvt... no
checking build system type... powerpc-apple-darwin6.6
checking host system type... powerpc-apple-darwin6.6
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... no
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -p
checking whether ln -s works... yes
checking how to recognise dependant libraries... file_magic Mach-O 
dynamically linked shared library
checking command to parse /usr/bin/nm -p output... ok
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... no
checking dlfcn.h presence... no
checking for dlfcn.h... no
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for gcc option to produce PIC... -fno-common
checking if gcc PIC flag -fno-common works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... 
yes
checking how to hardcode library paths into programs... unsupported
checking whether stripping libraries is possible... no
checking dynamic linker characteristics... darwin6.6 dyld
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/CLucene/Makefile
config.status: creating src/CLucene/analysis/Makefile
config.status: creating src/CLucene/analysis/standard/Makefile
config.status: creating src/CLucene/document/Makefile
config.status: creating src/CLucene/index/Makefile
config.status: creating src/CLucene/queryParser/Makefile
config.status: creating src/CLucene/search/Makefile
config.status: creating src/CLucene/store/Makefile
config.status: creating src/CLucene/util/Makefile
config.status: creating examples/Makefile
config.status: creating examples/demo/Makefile
config.status: creating examples/tests/Makefile
config.status: creating examples/util/Makefile
config.status: creating config.h
config.status: executing depfiles commands
[Jesse-Grosjeans-Computer:~/Desktop/clucene-0.8.1-src] jessegrosjean% 
make all
make  all-recursive
Making all in src
Making all in CLucene
Making all in analysis
Making all in standard
source='StandardAnalyzer.cpp' object='StandardAnalyzer.lo' libtool=yes \
depfile='.deps/StandardAnalyzer.Plo' 
tmpdepfile='.deps/StandardAnalyzer.TPlo' \
depmode=gcc3 /bin/sh ../../../.././build/gcc/config/depcomp \
/bin/sh ../../../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. 
-I../../../.. -I../../../../src    -g -O2 -c -o StandardAnalyzer.lo 
`test -f 'StandardAnalyzer.cpp' || echo './'`StandardAnalyzer.cpp
../../../../libtool: ../../../../libtool: No such file or directory
make[5]: *** [StandardAnalyzer.lo] Error 127
make[4]: *** [all-recursive] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
[Jesse-Grosjeans-Computer:~/Desktop/clucene-0.8.1-src] jessegrosjean%

//*******************************************************
// Second run
//*******************************************************

[Jesse-Grosjeans-Computer:~/Desktop/clucene-0.8.1-src] jessegrosjean% 
./bootstrap
mkdir: ./build/gcc/config: File exists
+ libtoolize --force --copy --ltdl --automake
+ aclocal
+ autoconf
+ autoheader
+ automake -a --copy --foreign
aclocal.m4:846: required file `./build/gcc/config/ltmain.sh' not found
[Jesse-Grosjeans-Computer:~/Desktop/clucene-0.8.1-src] jessegrosjean% 
./bootstrap
mkdir: ./build/gcc/config: File exists
+ libtoolize --force --copy --ltdl --automake
+ aclocal
+ autoconf
+ autoheader
+ automake -a --copy --foreign
[Jesse-Grosjeans-Computer:~/Desktop/clucene-0.8.1-src] jessegrosjean% 
./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for gcvt... no
checking build system type... powerpc-apple-darwin6.6
checking host system type... powerpc-apple-darwin6.6
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... no
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -p
checking whether ln -s works... yes
checking how to recognise dependant libraries... file_magic Mach-O 
dynamically linked shared library
checking command to parse /usr/bin/nm -p output... ok
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... no
checking dlfcn.h presence... no
checking for dlfcn.h... no
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for gcc option to produce PIC... -fno-common
checking if gcc PIC flag -fno-common works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... 
yes
checking how to hardcode library paths into programs... unsupported
checking whether stripping libraries is possible... no
checking dynamic linker characteristics... darwin6.6 dyld
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
creating libtool
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/CLucene/Makefile
config.status: creating src/CLucene/analysis/Makefile
config.status: creating src/CLucene/analysis/standard/Makefile
config.status: creating src/CLucene/document/Makefile
config.status: creating src/CLucene/index/Makefile
config.status: creating src/CLucene/queryParser/Makefile
config.status: creating src/CLucene/search/Makefile
config.status: creating src/CLucene/store/Makefile
config.status: creating src/CLucene/util/Makefile
config.status: creating examples/Makefile
config.status: creating examples/demo/Makefile
config.status: creating examples/tests/Makefile
config.status: creating examples/util/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
[Jesse-Grosjeans-Computer:~/Desktop/clucene-0.8.1-src] jessegrosjean% 
make all
cd . && /bin/sh 
/Users/jessegrosjean/Desktop/clucene-0.8.1-src/build/gcc/config/missing 
--run autoheader
touch ./config.h.in
cd . && /bin/sh ./config.status config.h
config.status: creating config.h
config.status: config.h is unchanged
make  all-recursive
Making all in src
Making all in CLucene
Making all in analysis
Making all in standard
source='StandardAnalyzer.cpp' object='StandardAnalyzer.lo' libtool=yes \
depfile='.deps/StandardAnalyzer.Plo' 
tmpdepfile='.deps/StandardAnalyzer.TPlo' \
depmode=gcc3 /bin/sh ../../../.././build/gcc/config/depcomp \
/bin/sh ../../../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. 
-I../../../.. -I../../../../src    -g -O2 -c -o StandardAnalyzer.lo 
`test -f 'StandardAnalyzer.cpp' || echo './'`StandardAnalyzer.cpp
rm -f .libs/StandardAnalyzer.lo
g++ -DHAVE_CONFIG_H -I. -I. -I../../../.. -I../../../../src -g -O2 -c 
StandardAnalyzer.cpp -MT StandardAnalyzer.lo -MD -MP -MF 
.deps/StandardAnalyzer.TPlo  -fno-common -DPIC -o 
.libs/StandardAnalyzer.lo
In file included from StandardAnalyzer.h:7,
                  from StandardAnalyzer.cpp:2:
../AnalysisHeader.h: In constructor 
`lucene::analysis::Token::Token(const
    char*, long int, long int)':
../AnalysisHeader.h:25: `1048576' cannot be used as a function
In file included from StandardAnalyzer.h:8,
                  from StandardAnalyzer.cpp:2:
../Analyzers.h: At global scope:
../Analyzers.h:258: `1048576' cannot be used as a function
../Analyzers.h:258: `1048576' cannot be used as a function
../Analyzers.h:258: `1048576' cannot be used as a function
../Analyzers.h:258: `1048576' cannot be used as a function
../Analyzers.h:258: `1048576' cannot be used as a function
../Analyzers.h:258: `1048576' cannot be used as a function
../Analyzers.h:258: `1048576' cannot be used as a function
../Analyzers.h:258: `1048576' cannot be used as a function
../Analyzers.h:259: `1048576' cannot be used as a function
../Analyzers.h:259: `1048576' cannot be used as a function
../Analyzers.h:259: `1048576' cannot be used as a function
../Analyzers.h:259: `1048576' cannot be used as a function
../Analyzers.h:259: `1048576' cannot be used as a function
../Analyzers.h:259: `1048576' cannot be used as a function
../Analyzers.h:260: `1048576' cannot be used as a function
../Analyzers.h:260: `1048576' cannot be used as a function
../Analyzers.h:260: `1048576' cannot be used as a function
../Analyzers.h:260: `1048576' cannot be used as a function
../Analyzers.h:260: `1048576' cannot be used as a function
../Analyzers.h:260: `1048576' cannot be used as a function
../Analyzers.h:260: `1048576' cannot be used as a function
../Analyzers.h:261: `1048576' cannot be used as a function
../Analyzers.h:261: `1048576' cannot be used as a function
../Analyzers.h:261: `1048576' cannot be used as a function
../Analyzers.h:261: `1048576' cannot be used as a function
../Analyzers.h:261: `1048576' cannot be used as a function
../Analyzers.h:261: `1048576' cannot be used as a function
../Analyzers.h:261: `1048576' cannot be used as a function
../Analyzers.h:262: `1048576' cannot be used as a function
../Analyzers.h:262: `1048576' cannot be used as a function
../Analyzers.h:262: `1048576' cannot be used as a function
../Analyzers.h:262: `1048576' cannot be used as a function
../Analyzers.h:262: `1048576' cannot be used as a function
../Analyzers.h:262: `1048576' cannot be used as a function
In file included from StandardFilter.h:7,
                  from StandardAnalyzer.h:9,
                  from StandardAnalyzer.cpp:2:
StandardTokenizerConstants.h:18: `1048576' cannot be used as a function
StandardTokenizerConstants.h:19: `1048576' cannot be used as a function
StandardTokenizerConstants.h:20: `1048576' cannot be used as a function
StandardTokenizerConstants.h:21: `1048576' cannot be used as a function
StandardTokenizerConstants.h:22: `1048576' cannot be used as a function
StandardTokenizerConstants.h:23: `1048576' cannot be used as a function
StandardTokenizerConstants.h:24: `1048576' cannot be used as a function
StandardTokenizerConstants.h:25: `1048576' cannot be used as a function
StandardTokenizerConstants.h:26: `1048576' cannot be used as a function
StandardTokenizerConstants.h:27: `1048576' cannot be used as a function
StandardTokenizerConstants.h:28: `1048576' cannot be used as a function
StandardTokenizerConstants.h:29: `1048576' cannot be used as a function
StandardTokenizerConstants.h:30: `1048576' cannot be used as a function
StandardTokenizerConstants.h:31: `1048576' cannot be used as a function
In file included from StandardAnalyzer.cpp:2:
StandardAnalyzer.h:20: `1048576' cannot be used as a function
StandardAnalyzer.h:20: `1048576' cannot be used as a function
StandardAnalyzer.h:20: `1048576' cannot be used as a function
StandardAnalyzer.h:20: `1048576' cannot be used as a function
StandardAnalyzer.h:20: `1048576' cannot be used as a function
StandardAnalyzer.h:20: `1048576' cannot be used as a function
StandardAnalyzer.h:20: `1048576' cannot be used as a function
StandardAnalyzer.h:20: `1048576' cannot be used as a function
StandardAnalyzer.h:21: `1048576' cannot be used as a function
StandardAnalyzer.h:21: `1048576' cannot be used as a function
StandardAnalyzer.h:21: `1048576' cannot be used as a function
StandardAnalyzer.h:21: `1048576' cannot be used as a function
StandardAnalyzer.h:21: `1048576' cannot be used as a function
StandardAnalyzer.h:21: `1048576' cannot be used as a function
StandardAnalyzer.h:22: `1048576' cannot be used as a function
StandardAnalyzer.h:22: `1048576' cannot be used as a function
StandardAnalyzer.h:22: `1048576' cannot be used as a function
StandardAnalyzer.h:22: `1048576' cannot be used as a function
StandardAnalyzer.h:22: `1048576' cannot be used as a function
StandardAnalyzer.h:22: `1048576' cannot be used as a function
StandardAnalyzer.h:22: `1048576' cannot be used as a function
StandardAnalyzer.h:23: `1048576' cannot be used as a function
StandardAnalyzer.h:23: `1048576' cannot be used as a function
StandardAnalyzer.h:23: `1048576' cannot be used as a function
StandardAnalyzer.h:23: `1048576' cannot be used as a function
StandardAnalyzer.h:23: `1048576' cannot be used as a function
StandardAnalyzer.h:23: `1048576' cannot be used as a function
StandardAnalyzer.h:23: `1048576' cannot be used as a function
StandardAnalyzer.h:24: `1048576' cannot be used as a function
StandardAnalyzer.h:24: `1048576' cannot be used as a function
StandardAnalyzer.h:24: `1048576' cannot be used as a function
StandardAnalyzer.h:24: `1048576' cannot be used as a function
StandardAnalyzer.h:24: `1048576' cannot be used as a function
StandardAnalyzer.h:24: `1048576' cannot be used as a function
make[5]: *** [StandardAnalyzer.lo] Error 1
make[4]: *** [all-recursive] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
[Jesse-Grosjeans-Computer:~/Desktop/clucene-0.8.1-src] jessegrosjean%
----------------------------------------------------------------
Jesse Grosjean
Hog Bay Software
www.hogbay.com/software/

[CLucene-dev] DLL Test

[Eduardo M. <em...@ac...>]

I compiled DLL Test using Visual Studio 2003 and got strange results. Take a
look at query results:

94. note: This is a stored note., date: Tue Sep 16 08:17:23 2003
95. note: This is a stored note., date: Tue Sep 16 08:17:23 2003
96. note: This is a stored note., date: Tue Sep 16 08:17:23 2003
97. note: This is a stored note., date: Tue Sep 16 08:17:23 2003
98. note: This is a stored note., date: Tue Sep 16 08:17:23 2003
99. note: This is a stored note., date: Tue Sep 16 08:17:23 2003
100. note: This is a stored note., date: Tue Sep 16 08:17:23 2003
101. note: (null), date: Wed Dec 31 22:00:00 1969
102. note: (null), date: Wed Dec 31 22:00:00 1969
103. note: (null), date: Wed Dec 31 22:00:00 1969
104. note: (null), date: Wed Dec 31 22:00:00 1969
105. note: (null), date: Wed Dec 31 22:00:00 1969
106. note: (null), date: Wed Dec 31 22:00:00 1969
107. note: (null), date: Wed Dec 31 22:00:00 1969
108. note: (null), date: Wed Dec 31 22:00:00 1969
109. note: (null), date: Wed Dec 31 22:00:00 1969
110. note: (null), date: Wed Dec 31 22:00:00 1969

I tried several times all with the same results. Examining the FTD file seem
it is ok. Also if I run the test several times in a sequences, without
erasing the directory, I always obtain the correct number of hits but only
the first 100 are correct.

Best regards,
Eduardo Mauro

Re: [CLucene-dev] development status

[<rg...@sd...>]

>>>>> "ben" == ben  <be...@vi...> writes:
ben> 
ben> Hi Everybody,
ben> I just wanted to put out a feeler of what people thought about
ben> clucene.  Mainly the status of it. Do people still think it is a
ben> beta product, or could it be classified as production?
ben> 
ben> Comments?

I wouldn't worry too much about classifying it as production or
non-production.  The real question is, does it do what you want it to
?  

I think it is close to production, although there are still bugs I
think.  (I'm trying to track one down now.)  I just ran it in valgrind
and saw some memory errors.

If someone asks you "should I use it ?  Is is production quality ?"
Tell them to try it and see . . .

--Rob

[CLucene-dev] development status

[<be...@vi...>]

Hi Everybody,

I just wanted to put out a feeler of what people thought about clucene.
Mainly the status of it. Do people still think it is a beta product, or
could it be classified as production?

Comments?

Thanks,
Ben

Re: [CLucene-dev] A Couple Questions

[<be...@vi...>]

Hi Neal,

In regards to your questions.
Number 1 was answered by Doug Cutting, which is also the case in CLucene.
As for number 2, unicode IS implemented, but is currently not built into
the autoscripts. It is just a matter of adding the precompiler directive
'_UNICODE' and hoping for the best (not tested on unix platforms). I have
it working on WIN32 with unicode with no problems.

You may be interested in ironing out the bugs in the new PHP plugin if you
want to use it ;)

regards,
ben

> Hey,
> 	I have a couple questions about CLucene implementation for you.
>
> 1)  One dissadvantage to an inverted index with words/terms as the key
> is that deleting a particular document from the index requires walking
> the entire index.  It can be overcome with maintentance of a
> document->term index that allows for faster deleting from the inverted
> index.  Do you address this at all?
>
> 2)  What are your Unicode plans?
>
> I work on HtDig and I'm curious ;-)
>
> Thanks for your time!
>
> Neal Richter

Re: [CLucene-dev] OS X

[<rg...@sd...>]

>>>>> "Jesse" == Jesse Grosjean <jgr...@go...> writes:
Jesse> 
Jesse> Rob,
Jesse> 
Jesse> Thanks for offering your help. Well your "fink" suggestion got
Jesse> me off on the right track. At the start the clucene build
Jesse> process complained that I didn't have the correct version of
Jesse> autoconf, and i was unsure of how to get it. But fink did that
Jesse> nicely and now the build process goes much further.
Jesse> 
Jesse> Everything seems to go to plan in the beginning except for this
Jesse> message:
Jesse> 
Jesse> 	aclocal.m4:846: required file `./build/gcc/config/ltmain.sh' not found
Jesse> 
Jesse> But then in the end when it actually starts trying to compile I
Jesse> see more problems. Please let me know were I should look
Jesse> next. I've included my entire terminal transcript below.

I think ltmain.sh is part of the libtool package, and the error
message towards the end also mentions libtool.

Can you run "libtool --version" at the command line and get a version
number ?  I am compiling libtool with version 1.5a.  If you have no
libtool, or if fink's libtool is old, you might have to download and
install a newer libtool.

I regret that at the moment I do not have access to an OS X machine to
test things on with you.  However, I might have access to one after
the end of the month.

If you are missing libtool or have an old version, that might explain
things.

--Rob

Re: [CLucene-dev] A Couple Questions

[Doug C. <cu...@lu...>]

Neal Richter wrote:
> 1)  One dissadvantage to an inverted index with words/terms as the key is
> that deleting a particular document from the index requires walking the
> entire index.  It can be overcome with maintentance of a document->term
> index that allows for faster deleting from the inverted index.  Do you
> address this at all?

In Lucene, documents are marked as deleted, so that they do not appear 
in search results, but the inverted lists are not altered.  All index 
modification is then done by copying.  When a segment of the index is 
copied (triggered either by documents being added, or when the index is 
explicitly optimized) then the space consumed by deleted documents is 
reclaimed.  Index optimization does require walking the entire index. 
In practice, this is needed seldom enough that it's not a problem.

At least this is the case for Java Lucene, and, from what I know, 
CLucene works similarly.  (I trust the CLucene developers will correct 
me if I'm wrong here.)

Doug

Re: [CLucene-dev] OS X

[Jesse G. <jgr...@go...>]

> What are your error messages ?  Or perhaps you don't know where to
> begin ?
>
> OS X should not be different enough to present a problem.  After
> possibly adding some tools with that fink package, the next likely
> problem would be making the build system work.
>
> It is likely that we can help you get it working if you send the error
> messages.

Rob,

Thanks for offering your help. Well your "fink" suggestion got me off  
on the right track. At the start the clucene build process complained  
that I didn't have the correct version of autoconf, and i was unsure of  
how to get it. But fink did that nicely and now the build process goes  
much further.

Everything seems to go to plan in the beginning except for this message:

	aclocal.m4:846: required file `./build/gcc/config/ltmain.sh' not found

But then in the end when it actually starts trying to compile I see  
more problems. Please let me know were I should look next. I've  
included my entire terminal transcript below.

Thanks for your help,
Jesse

[Jesse-Grosjeans-Computer:~/Desktop/clucene-0.8.1-src] jessegrosjean%  
./bootstrap
mkdir: ./build/gcc/config: File exists
+ libtoolize --force --copy --ltdl --automake
./bootstrap: libtoolize: command not found
+ aclocal
+ autoconf
+ autoheader
+ automake -a --copy --foreign
aclocal.m4:846: required file `./build/gcc/config/ltmain.sh' not found
[Jesse-Grosjeans-Computer:~/Desktop/clucene-0.8.1-src] jessegrosjean%  
cd build/gcc/
[Jesse-Grosjeans-Computer:clucene-0.8.1-src/build/gcc] jessegrosjean%  
../../configure CXXFLAGS="-g -DCOMPILER_GCC" CFLAGS="-g -DCOMPILER_GCC"  
--prefix=/home/`whoami`/clucene_test
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for gcvt... no
checking build system type... powerpc-apple-darwin6.6
checking host system type... powerpc-apple-darwin6.6
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... no
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -p
checking whether ln -s works... yes
checking how to recognise dependant libraries... file_magic Mach-O  
dynamically linked shared library
checking command to parse /usr/bin/nm -p output... ok
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... no
checking dlfcn.h presence... no
checking for dlfcn.h... no
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for gcc option to produce PIC... -fno-common
checking if gcc PIC flag -fno-common works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/bin/ld) supports shared libraries...  
yes
checking how to hardcode library paths into programs... unsupported
checking whether stripping libraries is possible... no
checking dynamic linker characteristics... darwin6.6 dyld
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/CLucene/Makefile
config.status: creating src/CLucene/analysis/Makefile
config.status: creating src/CLucene/analysis/standard/Makefile
config.status: creating src/CLucene/document/Makefile
config.status: creating src/CLucene/index/Makefile
config.status: creating src/CLucene/queryParser/Makefile
config.status: creating src/CLucene/search/Makefile
config.status: creating src/CLucene/store/Makefile
config.status: creating src/CLucene/util/Makefile
config.status: creating examples/Makefile
config.status: creating examples/demo/Makefile
config.status: creating examples/tests/Makefile
config.status: creating examples/util/Makefile
config.status: creating config.h
config.status: executing depfiles commands
[Jesse-Grosjeans-Computer:clucene-0.8.1-src/build/gcc] jessegrosjean%  
make install
Making install in src
Making install in CLucene
Making install in analysis
Making install in standard
source='../../../../../../src/CLucene/analysis/standard/ 
StandardAnalyzer.cpp' object='StandardAnalyzer.lo' libtool=yes \
depfile='.deps/StandardAnalyzer.Plo'  
tmpdepfile='.deps/StandardAnalyzer.TPlo' \
depmode=gcc3 /bin/sh ../../../../../.././build/gcc/config/depcomp \
/bin/sh ../../../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I.  
-I../../../../../../src/CLucene/analysis/standard -I../../../..  
-I../../../../../../src    -g -DCOMPILER_GCC -c -o StandardAnalyzer.lo  
`test -f  
'../../../../../../src/CLucene/analysis/standard/StandardAnalyzer.cpp'  
|| echo  
'../../../../../../src/CLucene/analysis/standard/'`../../../../../../ 
src/CLucene/analysis/standard/StandardAnalyzer.cpp
../../../../libtool: ../../../../libtool: No such file or directory
make[4]: *** [StandardAnalyzer.lo] Error 127
make[3]: *** [install-recursive] Error 1
make[2]: *** [install-recursive] Error 1
make[1]: *** [install-recursive] Error 1
make: *** [install-recursive] Error 1


On Wednesday, September 10, 2003, at 02:02  AM, Rob Ristroph wrote:

----------------------------------------------------------------
Jesse Grosjean
Hog Bay Software
www.hogbay.com/software/

[CLucene-dev] A Couple Questions

[Neal R. <ne...@ri...>]

Hey,
	I have a couple questions about CLucene implementation for you.

1)  One dissadvantage to an inverted index with words/terms as the key is
that deleting a particular document from the index requires walking the
entire index.  It can be overcome with maintentance of a document->term
index that allows for faster deleting from the inverted index.  Do you
address this at all?

2)  What are your Unicode plans?

I work on HtDig and I'm curious ;-)

Thanks for your time!

Neal Richter
Knowledgebase Developer
RightNow Technologies, Inc.
Customer Service for Every Web Site
Office: 406-522-1485

Re: [CLucene-dev] OS X

[<rg...@sd...>]

>>>>> "Jesse" == Jesse Grosjean <jgr...@go...> writes:
Jesse> 
Jesse> is anyone out there using OS X? I'm currently using java lucene
Jesse> on OS X and am very happy with it, but would like to switch to
Jesse> clucene for performance and memory use improvements. But i'm a
Jesse> bit of a newbi with make files and such and cant seem to build
Jesse> the clucene library properly. Has anyone out there accomplished
Jesse> this?
Jesse> 
Jesse> Thanks,
Jesse> Jesse

What are your error messages ?  Or perhaps you don't know where to
begin ?

OS X should not be different enough to present a problem.  After
possibly adding some tools with that fink package, the next likely
problem would be making the build system work.

It is likely that we can help you get it working if you send the error
messages.

--Rob

Re: [CLucene-dev] problems accessing anonymous cvs

[<rg...@sd...>]

>>>>> "Doug" == Doug Cutting <cu...@lu...> writes:
Doug> 
Doug> Rob Ristroph wrote:
>> However I think that SF's cvs server may be temporarily down.  I can't
>> even do the login step right now.  I'll try again tomorrow.
Doug> 
Doug> My advice with SourceForge CVS is, when it fails, try again a
Doug> few times and it usually works.  Sometimes it is truly
Doug> unavailable too.  It's currently underpowered, but they're
Doug> adding more servers real soon now.
Doug> 
Doug> 
Doug> http://sourceforge.net/docman/display_doc.php?docid=2352&group_id=1#cvs
Doug> 
Doug> Doug

I have successfully checked out, and then updated afterwards.
Persistence was the key.  Thanks.

--Rob

[CLucene-dev] OS X

[Jesse G. <jgr...@go...>]

is anyone out there using OS X? I'm currently using java lucene on OS X 
and am very happy with it, but would like to switch to clucene for 
performance and memory use improvements. But i'm a bit of a newbi with 
make files and such and cant seem to build the clucene library 
properly. Has anyone out there accomplished this?

Thanks,
Jesse

----------------------------------------------------------------
Jesse Grosjean
Hog Bay Software
www.hogbay.com/software/