There isn't going to be a 2.1.4 (unless Dennis wants to make one from his tree - AFAIC there isn't enough change to be worth it).
And, no, we're not ready for 2.1.52 until 1. the rrd stuff shakes out 2. we have a way of building ntop that works I'm working on a complete re-write of the configure.in/Makefile.am set. Luca would like me to get that done ASAP and in, so we can shake it down. If I do that, there are a couple of things to be aware of (all of which will delay 2.1.52): 1. I'm going to reduce/eliminate a lot of the (fragile)(hand-coded) molly coddling we have. This means that if a tool isn't installed where it's accessible via the normal #include and libraries (e.g. ld.so.conf), it's not going to be found. And you'll have to specify it's location with the --with-xxxx-root parameter. This will cause some angst, such as in the case of (flipping) RedHat, which puts pcap.h in /usr/include/pcap/ not /usr/include! 2. I've changed the look/feel - it does all the AC_CHECK_xxxxs and THEN analyzes the results, so the meaningful errors and warnings are at the bottom - harder to ignore. 3. Errors, warnings, notes etc. are in BIG BOXES of ***S 4. There are some places where we should cleanup code and use the HAVE_xxxx's instead. But I hope to get the auto* working first, THEN cleanup the code. It means that some oddball configurations might not work at first, s'be'it... that's why it's a DEVELOPMENT version... Here's an abbreviated output: Welcome to ntop, Version 2.1.51 copyright (c) 1998-2002 Luca Deri <[EMAIL PROTECTED]> Configuring ntop according to your request(s): ./configure --prefix=/usr ******************************************************************* * * * NOTICE: I know you're used to ignoring output from ./configure * * * * ntop has a lot of complexity and interdependences. * * * * Please, please AT LEAST read the stuff in these * * boxes! * * * *>>> The ACTION taken is shown prefixed '>>>' * * * * If the ACTION is unacceptable, * *??? The REMEDIATION plan is shown prefixed with '???' * * * ******************************************************************* checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu ... 10 pages snipped ... checking for sem_init in -lposix4... no checking for hosts_access in -lwrap... no checking for rrd_create in -lrrd... no Now, let's check for problems with what we've found... **Required headers** **Required libraries** pcap: ******************************************************************* * * * ERROR: 1. We were unable to find the header pcap.h and/or * * the libary in the standard locations. * * * * and 2. You did not specify an alternate location * * via --with-pcap-root. * * * *>>> No way to proceed. * * * *??? 1. Install libpcap and rerun ./configure * *??? or 2. rerun ./configure with --with-pcap-root * * * ******************************************************************* -----Original Message----- From: [EMAIL PROTECTED] [mailto:ntop-admin@;unipi.it]On Behalf Of Arnt Karlsen Sent: Thursday, October 17, 2002 3:50 AM To: [EMAIL PROTECTED] Subject: Re: [Ntop] Say hello to RRDtool On Thu, 17 Oct 2002 09:37:10 +0200, Luca Deri <[EMAIL PROTECTED]> wrote in message <[EMAIL PROTECTED]>: > Tony, > bug fixed. Please resync. > > Thanks for reporting it. > > Cheers, Luca ..are we ready for 2.1.4 and 2.1.52? :-) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
