At 12:29 AM -0600 9/12/00, Jim Cole wrote:
>1. Linux odin 2.2.14  i586 unknown
>    gcc 2.95.2
>
>    Build successful. One test failed.

Which test was this?

>2. Linux magni 2.2.15pre14  ppc unknown
>    gcc 2.95.2
>
>    Build successful. Tests fail miserably with two or three core dumps
>    along the way.

Boy do I know. That's my build platform. I'm looking into this, 
though strangely enough the current mifluz build is clean.

>3. FreeBSD loki 3.2-RELEASE FreeBSD 3.2-RELEASE  i386
>    gcc 2.7.2.1
>
>    Build fails. htlib/md5.cc needs to include <sys/time.h> or something
>    similar so that time_t is defined. After this change, the build was
>    successful. Three tests failed.
>
>4. SunOS thor 5.7 Generic sun4m sparc SUNW,SPARCclassic
>    egcs-2.91.66
>
>    Build fails. htlib/md5.cc needs to include <sys/time.h> or something
>    similar so that time_t is defined. The build again fails at line 132
>    of htnet/HtFile.cc. This is due to alphasort falling into the category
>    of "SunOS/BSD Compatibility Library Functions". As far as I know, the
>    only place alphasort is defined is in /usr/ucbinclude/sys/dir.h However,
>    if this file is included, with or without dirent.h, things turn ugly.
>    And this is about where I decided it was bed time ;)

I'll try to get onto a Sun box soon and hunt around for alphasort and 
ways to get that code to compile. Obviously a lot of people want 
their directory indexes. :-) If someone has access to a Solaris box 
and can work it out, so much the better--it's going to be a busy week 
for me.

I can generally decipher test results, but at the least it's good to 
know which test was failing.

Thanks,
-Geoff


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


Reply via email to