I'm tracking down the problem. The original configure script (build bij autoconf 2.57) creates a C-program where HP-UX gcc chokes on, screaming that there are more than one prototype definitions for select.
Autoconfing the configure.in script using autoconf 2.13 produces a different C-program and .. tada(.wav)! The select problem is gone. Actually, I took the select part from the 2.13 version and placed it over the 2.57 part. But now it breaks on the compile part saying something about ambigious declarations. Later more on that. I will make a file containing the original 2.57 select test and the 2.13 select test. Maybe someone with knowledge on autoconf can change it. ----- Original Message ----- From: "Lachlan Andrew" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, June 08, 2003 7:20 AM Subject: [htdig-dev] 3.2.0b4 Progress check :) > Greetings all, > > Thank you to everybody for your work towards getting 3.2.0b5 out. > > Could people doing specific tasks give an update on how they're going, > and what others of us can do to help? > > Geoff: Did you manage the copyright update? If you have written the > sed script, but haven't had time to apply/commit, could you please > post it? I should have some time this week to do that. > > Gilles: How is the Latin encodings going? If it is simply a forward > port, I can try it. If you want new features, I'll leave it to you. > > Neal: It's good to hear that you're coming along with the Win32 port. > >From where I'm standing, the highest priority is applying the > memory-leak patch, so that the rest of us can test it thoroughly. > Could you please do that some time this week? > > Jess: Any luck with the HP-UX configuration? If you post the > config.log then one of the rest of us might have an idea why it is > failing. > > Does the following timeline sound feasible? > This time, I think the showstoppers are gone, so we can afford to set > a firm timeline (although not necessarily this one :) > > Sun 8 - Fri 13: Finalise Unix code / configuration > Update copyright > Other documentation updates? > Weekend 14-15: Unix code freeze, and re-test all available platforms > Ask "non-team" volunteers to "install/make check" the snapshot > Mon 16-Fri 20: Finish Win32, or decide to postpone until 3.2.0b6 > Further documentation updates? > Testing by non-team volunteers > Weekend 21-22: Code freeze > Test Win32 (if finished) > Rename 3.2.0b4->3.2.0b5 > Mon 23: BETA RELEASE > > What docs need to be updated? The www.htdig.org FAQ is much bigger > than the distribution FAQ. Should it be copied over (even though a > lot of it relates to 3.1)? > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of TotalView, The best > thread debugger on the planet. Designed with thread debugging features > you've never dreamed of, try TotalView 6 free at www.etnus.com. > _______________________________________________ > htdig-dev mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/htdig-dev > ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ htdig-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
