Everything compiles, but there are a few warnings. The most common warning is due to the fact that /usr/include is explicitly provided via -I. This at least has the potential to create other problems. According to the GCC documentation...
If a standard system include directory, or a directory specified with -isystem, is also specified with -I, it will be searched only in the position requested by -I. Also, it will not be considered a system include directory. If that directory really does contain system headers, there is a good chance that they will break. For instance, if GCC's installation procedure edited the headers in /usr/include to fix bugs, -I/usr/include will cause the original, buggy headers to be found instead of the corrected ones. GCC will issue a warning when a system include directory is hidden in this way.
I think this only affects version 3.1, with explicit specification of system include directories being ignored in 3.2 and 3.3.
Another frequent warning is the following.
warning: redeclaration of C++ built-in type `wchar_t'
I think this warning results from the problem introduced by explicitly specifying system include directories. Since /usr/include is no longer considered a system include directory, files in that directory are seen as redeclaring wchar_t. Well, that is my guess anyway.
A couple other warnings involve lex.
In file included from conf_lexer.cxx:24:
/usr/include/stdlib.h:77: warning: redeclaration of C++ built-in type `wchar_t'
conf_lexer.cxx: In function `int yylex()':
conf_lexer.cxx:704: warning: label `find_rule' defined but not used
/usr/include/gcc/darwin/3.1/g++-v3/streambuf: At top level:
conf_lexer.cxx:1790: warning: `void* yy_flex_realloc(void*, unsigned int)'
defined but not used
Finally, there are three link warnings (repeated multiple times) involving multiple definitions of _regcomp, _regexec, and _regfree. They look something like
ld: warning multiple definitions of symbol _regcomp
../htlib/.libs/libht.a(regex.o) definition of _regcomp in section (__TEXT,__text)
/usr/lib/libSystem.dylib(regcomp.So) definition of _regcomp
As for 'make check' the code now compiles (with the same warnings as above) and all tests pass. There is one possible glitch in that an attempt to find HtFileType fails. The output generated by 'make check' includes
PASS: t_htmerge
PASS: t_htnet
sh: /Users/greyleaf/local/htdig_cvs/bin/HtFileType: No such file or directory
PASS: t_htdig_local
===================
All 14 tests passed
Checking after the fact, the file appears to be there.
The only other issue that I encountered involves htfuzzy. Processing of synonyms generates the following output.
htfuzzy/synonyms: 1500 willfull htfuzzy/synonyms: 1510 woolie htfuzzy/synonyms: Rejected line with less than 2 words:
htfuzzy/synonyms: 1519 worshipping htfuzzy/synonyms: Done. htfuzzy: Done.
The 'Rejected' notice appears to be due to the blank line at the end of the synonyms file.
Aside from the above (and the known issue with dynamic builds) things seem to be working reasonably well. I have tried a couple digs and have not encountered any crashes or noticeable database corruption; I do have compression enabled.
Jim
------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge _______________________________________________ htdig-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
