From: Martin L. <mar...@fi...> - 2003-02-19 16:46:22
|
Hi guys, I'm new to this list and so please don't flame me if i ask this questio= n again: I try to compile the 3.2.0.b3 Version on an AIX 5.1L Partition using gc= c 2.9-aix51-020209 on a RS6000 (IBM Regatta). What i need from the newer Version is the ph= rases feature. During the compilation phase i got theese warnings: lock_region.c: In function `CDB___lock_dump_object': lock_region.c:630: warning: format not a string literal, argument types= not checked strptime.cc: In function `char *mystrptime (const char *, const char *,= tm *)': strptime.cc:86: warning: `int len' might be used uninitialized in this = function In file included from WordDBCompress.cc:22: WordDBPage.h: In method `void WordDBPage::insert_btikey (WordDBKey &, B= INTERNAL &, int)': WordDBPage.h:267: warning: int format, long int arg (arg 2) WordDBPage.h:267: warning: int format, long int arg (arg 3) WordDBPage.h: In method `void WordDBPage::compress_key (Compressor &, i= nt)': WordDBPage.h:323: warning: int format, long int arg (arg 3) In file included from WordDBPage.cc:19: WordDBPage.h: In method `void WordDBPage::insert_btikey (WordDBKey &, B= INTERNAL &, int)': WordDBPage.h:267: warning: int format, long int arg (arg 2) WordDBPage.h:267: warning: int format, long int arg (arg 3) WordDBPage.h: In method `void WordDBPage::compress_key (Compressor &, i= nt)': WordDBPage.h:323: warning: int format, long int arg (arg 3) WordMonitor.cc: In method `void WordMonitor::TimerStart ()': WordMonitor.cc:176: warning: long int format, time_t arg (arg 3) defaults.cc:184: warning: white space at end of line in string ... defaults.cc:2478: warning: white space at end of line in string conf_lexer.cxx: In function `int yylex ()': conf_lexer.cxx:705: warning: label `find_rule' defined but not used conf_lexer.cxx: At top level: conf_lexer.cxx:1784: warning: `void *yy_flex_realloc (void *, unsigned = int)' defined but not used Synonym.cc: In method `int Synonym::createDB (const HtConfiguration &)'= : Synonym.cc:84: warning: choosing `String::operator char * ()' over `String::operator const char * () const' Synonym.cc:84: warning: for conversion from `String' to `const char *= ' Synonym.cc:84: warning: because conversion sequence for the argument = is better Server.cc: In method `Server::Server (URL, StringList *)': Server.cc:52: warning: choosing `String::operator char * ()' over `String::operator const char * () const' Server.cc:52: warning: for conversion from `String' to `const char *'= Server.cc:52: warning: because conversion sequence for the argument i= s better Server.cc:55: warning: choosing `String::operator char * ()' over `String::operator const char * () const' Server.cc:55: warning: for conversion from `String' to `const char *'= Server.cc:55: warning: because conversion sequence for the argument i= s better Server.cc:58: warning: choosing `String::operator char * ()' over `String::operator const char * () const' Server.cc:58: warning: for conversion from `String' to `const char *'= Server.cc:58: warning: because conversion sequence for the argument i= s better Server.cc:61: warning: choosing `String::operator char * ()' over `String::operator const char * () const' Server.cc:61: warning: for conversion from `String' to `const char *'= Server.cc:61: warning: because conversion sequence for the argument i= s better Server.cc:123: warning: `HtHTTP *http' might be used uninitialized in t= his function Display.cc: In method `void Display::setVariables (int, List *)': Display.cc:621: warning: choosing `String::operator char * ()' over `String::operator const char * () const' Display.cc:621: warning: for conversion from `String' to `const char = *' Display.cc:621: warning: because conversion sequence for the argument= is better Display.cc:623: warning: choosing `String::operator char * ()' over `String::operator const char * () const' Display.cc:623: warning: for conversion from `String' to `const char = *' Display.cc:623: warning: because conversion sequence for the argument= is better At least I got my binaries, linking lstdc++ and lm against it. But when i try to use them e.g. htfuzzy to begin to build up the first = .db for the endings, it got an exception like "illegal instruction" a core but not able to backtrac= e. When i start htfuzzy verry verbosely i got something like this: tfuzzy: Selected algorithm: endings htfuzzy/endings: Reading rules htfuzzy/endings: Creating databases Applying regex '^.*.$' to =E4bte =E4bte with n --> '=E4bten' Illegal instruction (core dumped) The same with the digger itself: Rejected: URL not in the limits! url rejected: (level 1)http://xyz.fiducia.de/fiducia/brettall.nsf/Datum= ?OpenView image: http://xyz.fiducia.de/img/foldoutmenu_arrow_closed.gif href: http://xyz.fiducia.de/fiducia/brettall.nsf/kategorie?OpenView (Ka= tegorie) Rejected: URL not in the limits! url rejected: (level 1)http://xyz.fiducia.de/fiducia/brettall.nsf/kategorie?OpenView size =3D 3530 Illegal instruction (core dumped) I'm not the specialist for the gdb to trace anything, but when I backtr= ace (that's wat i know) the gdb shows me something like: GNU gdb 5.0-aix51-020209 Copyright 2000 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and yo= u are welcome to change it and/or distribute copies of it under certain condi= tions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for deta= ils. This GDB was configured as "powerpc-ibm-aix5.1.0.0"... Core was generated by `htdig'. Program terminated with signal 4, Illegal instruction. #0 0x0 in ?? () from (unknown load module) (gdb) bt #0 0x0 in ?? () from (unknown load module) #1 0x100e92a4 in HtHeap::pushDownRoot (this=3D0x212ed894, root=3D0) at= HtVector.h:65470 #2 0x100e8ec8 in HtHeap::Remove (this=3D0x212ed894) at HtHeap.cc:103 #3 0x100e8464 in Server::pop (this=3D0x214eac58) at Server.cc:342 #4 0x100c8d6c in Retriever::Start (this=3D0x2ff21fb8) at Retriever.cc:= 428 #5 0x100012b8 in main (ac=3D5, av=3D0x2004d124) at htdig.cc:317 #6 0x100001dc in __start () I know that there were some people before, who had some problems on Sun= Solaris or HP UX11. Is some body out there who compiled this horse on a 64Mbit (RS600= 0 (big Endian)) System and keep that horse running? What do i have to care on? Any suggestions are welcome! Thanks Martin Laarz --------------------- FIDUCIA AG Karlsruhe/Stuttgart Wachhausstra=DFe 4 76227 Karlsruhe Martin Laarz Wissensmanager Technik Tel.: 07 21 / 4004 - 2861 mailto: mar...@fi... Fax: 07 21 / 4004 - 1176 Web: http://www.fiducia.de = |
From: Gilles D. <gr...@sc...> - 2003-02-19 18:00:55
|
According to Martin Laarz: > I try to compile the 3.2.0.b3 Version on an AIX 5.1L Partition using gcc > 2.9-aix51-020209 > on a RS6000 (IBM Regatta). What i need from the newer Version is the phrases > feature. > > During the compilation phase i got theese warnings: ... > At least I got my binaries, linking lstdc++ and lm against it. > > But when i try to use them e.g. htfuzzy to begin to build up the first .db for > the endings, it got > an exception like "illegal instruction" a core but not able to backtrace. Well, at the very least, I recommend you dump 3.2.0b3, and try the latest 3.2.0b4 development snapshot from http://www.htdig.org/files/snapshots/ -- Gilles R. Detillieux E-mail: <gr...@sc...> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) |