Author: Kian Hoe
Email: [EMAIL PROTECTED]
Message:
Hi,

I am using Mnogosearch 3.2.3 to index all my Big5 encoded documents. The indexing went 
well. However, when I do a search, search.cgi only returns documents that were created 
on a particular day. There are many other documents which match the entered keyword. 
Somehow, search.cgi just miss them out. Any suggestions what I should look out for?

My settings are as follow:

DBAddr  pgsql://myid:[EMAIL PROTECTED]/mnogosearch/
DBMode  crc-multi
LocalCharset   big5
BrowserCharset big5
I am expecting search.cgi to return hundreds of matches instead of just 13 of them. I 
went to the url table to check and it seems to me that all the documents are indexed 
by the indexer.

By the way, I saw some errors when I run make install. Not sure is it related to this 
problem. Please help. Thank you very much.

**************************************************************

 /usr/bin/install -c -m 644 ../include/udm_header.h 
/home/search/mnogosearch/include/../include/udm_header.h
/usr/bin/install: `../include/udm_header.h' and 
`/home/search/mnogosearch/include/../include/udm_header.h' are the same
file
 /usr/bin/install -c -m 644 ../include/udm_store.h 
/home/search/mnogosearch/include/../include/udm_store.h
/usr/bin/install: `../include/udm_store.h' and 
`/home/search/mnogosearch/include/../include/udm_store.h' are the same fi
le
 /usr/bin/install -c -m 644 ../include/udm_template.h 
/home/search/mnogosearch/include/../include/udm_template.h
/usr/bin/install: `../include/udm_template.h' and 
`/home/search/mnogosearch/include/../include/udm_template.h' are the s
ame file
make[2]: *** [install-includeHEADERS] Error 1
make[2]: Leaving directory `/home/search/mnogosearch/src'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/home/search/mnogosearch/src'
make: *** [install-recursive] Error 1



Reply: <http://www.mnogosearch.org/board/message.php?id=4005>

___________________________________________
If you want to unsubscribe send "unsubscribe general"
to [EMAIL PROTECTED]

Reply via email to