Can anyone comment on what would be required to make the htdig 3.2b4 code 64 bit clean ?
I'm not familiar with issues on Solaris, but ht://Dig has long been "clean" on Alpha systems. So it should be 64-bit clean as-is. The Berkeley DB code is most definitely 64-bit clean and handles databases up to 4TB if you've got the hardware for it.
I am merging large databases, and the htmerge requires >4Gb memory so I have had to compile using -m64 (Solaris 8, gcc 3.2.1) but had to make some small changes in the code to make it compile, and to avoid a segmentation error.
OK, what changes did you make exactly? What snapshot did you use? Are you attempting to compile/use shared libraries?
I am indexing > 400,000 pages - any thoughts on whether htdig 3.3 can scale to this ?
I'm curious why this is causing problems. I know people who have 32-bit systems that easily handle 400,000+ pages. How big are your databases exactly? Are your problems limited to htmerge? (In which case, I likely know the problem, and it's not due to 64-bit addressing.)
-Geoff
-- -Geoff Hutchison Williams Students Online http://wso.williams.edu/
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
