According to Randall Fish: > Please excuse me for the dumb question but: > How do I compile db_dump.c under CYGWIN version 2.249.2.5 in Htdig > Version 3.1.6?
Actually, that's a good question. There's no Makefile to go with it. I'd suggest taking a look at how the rest of the db code is compiled when you do a "make", and use the same compile options for db_dump.c. As for linking, I think you'll need to include db/dist/libdb.a on the cc command so that the appropriate database code is linked in. Without having Cygwin here, I can't really get more specific than that. > I recreate the index from scratch every day using a dos batch file. > c:\htdig\bin\htdig -v -s -a > c:\htdig\bin\diglog.txt > IF ERRORLEVEL 1 GOTO :ENDFILE > c:\htdig\bin\htmerge -v -a > c:\htdig\bin\mergelog.txt > IF ERRORLEVEL 1 GOTO :ENDFILE > > DEL c:\htdig\db\*.bak > REN c:\htdig\db\db.docdb db.docdb.bak > REN c:\htdig\db\db.docs.index db.docs.index.bak > REN c:\htdig\db\db.wordlist db.wordlist.bak > REN c:\htdig\db\db.words.db db.words.db.bak > REN c:\htdig\db\db.docdb.work db.docdb > REN c:\htdig\db\db.docs.index.work db.docs.index > REN c:\htdig\db\db.wordlist.work db.wordlist > REN c:\htdig\db\db.words.db.work db.words.db > > :ENDFILE > > I could search for some of the lost terms on Friday and after > the batch file was run again the terms cannot be found. > > Memory has been added to our server since Htdig was last compiled. > Should I try recompiling? I don't know Cygwin well enough to know whether recompiling/relinking is needed after adding memory. It seems awfully unlikely to me. Then again, a recompile shouldn't hurt either, so it may be worth a try. > Randall ><> > > > Yet, lost entries in db.words.db seems to be the most reasonable > > explanation for this problem. About all I can think to suggest right > > now is to try compiling and running db/db_dump/db_dump.c to look at the > > entries in db.words.db and see if anything is missing. If entries are > > missing, then htmerge isn't building this db correctly under Cygwin. > > If the db is complete, then htsearch doesn't seem to be finding all the > > entries under Cygwin, or is rejecting them for some unknown reason. > > > Oh, have you tried reindexing from scratch to see if that makes the > > problem go away? It may be that the database has become corrupted > > somehow. (Although htmerge rebuilds db.words.db from scratch each time > > you run it, it may be that htsearch is dropping results because of a > > corrupted db.docdb.) Does the number of matches reported by htsearch > > agree with how many results are actually shown? -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
