According to David Adams:
> I use the standard MIPSpro compiler.  The script I use (thanks to my former 
> collegeaue James Hammick) to setup the Makefile is:
> 
> #!/bin/sh
> CFLAGS="-woff all -O2 -mips4 -n32 -DHAVE_ALLOCA_H" ; export CFLAGS
> CPPFLAGS="-woff all -O2 -mips4 -n32 -DHAVE_ALLOCA_H" ; export CPPFLAGS
> LDFLAGS="-mips4 -L/usr/lib32 -rpath /opt/local/htdig-3.1.5/lib";
> export LDFLAGS
> ./configure --prefix=/opt/local/htdig-3.1.5 \
>   --with-cgi-bin-dir=/opt/local/htdig-3.1.5/cgi-bin \
>   --with-image-dir=/opt/local/htdig-3.1.5/graphics \
>   --with-search-dir=/opt/local/htdig-3.1.5/htdocs/sample
> 
> A lot of that is site-specific, and the "-rpath <directory>" option is only
> needed because the compression library is not in a standard place on the 
> machine on which htdig is run.
> 
> The "-woff all" option suppresses most warning messages.  I will remove it,
> recompile htdig and send the result directly to Gilles, it might contain a clue.

As Sinclair mentioned, 'you need to have the 2.95.2 gcc and the latest
gnu "make".'  I don't know that anyone has ever gotten ht://Dig to work
with SGI's own compiler.  If fact, we got a lot of reports from folks
who couldn't even get it to compile.

If you're really determined to get to the bottom of this and make it work
with the SGI compiler, I wish you well, but I doubt I can help much.
I looked at the output you sent me, and didn't really see any red
flags pointing to an obvious problem.  I know that the Serialize and
Deserialize functions for the db.docdb records can be a tad finicky, so
that would probably be a place to look.  There could also be problems
with incorrect assumptions about word sizes, e.g. if the SGI compiler
has 64-bit long ints.  I'd also look at the db.wordlist records (they're
ASCII text) before and after htmerge, to see if htdig is actually telling
htmerge to remove some of these documents, or if htmerge is deciding to
do so on its own.

For the time being, the ht://Dig code hasn't had much of a workout on
non-GNU compilers, so it doesn't seem to do well on them.  If you can
help remedy that, great.  If you want to get the package working as
quickly and easily as possible, I'd suggest trying the GNU C and C++
compilers.

-- 
Gilles R. Detillieux              E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre       WWW:    http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba  Phone:  (204)789-3766
Winnipeg, MB  R3E 3J7  (Canada)   Fax:    (204)789-3930

------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.

Reply via email to