Could be - that's the nature of a cvs. In fact, in another msg, Luca says he's fixed it.
As I've said, the cvs is a development version. Sometimes rapidly moving, sometimes not. Sometimes a commit will break something on another OS or be total crud. It happens. If you're going to track the cvs, then keep an eye on the commit messages that show up here - it tells you what's being changed. Unfortunately, sometimes messages get lost or don't appear in a timely manner. In that case, cvs log and cvs diff are your friends... If something breaks, then apply the old 'what changed' filter and report the problem here. And as the version.xml warning says, "This is the current DEVELOPMENT version - Expect the unexpected!". I don't know why my periodic update didn't get the same files - maybe the server was offline and my script didn't catch it. But I've seen too many cases where people checked out into an existing directory, got half of a stable version and half of a cvs and it didn't compile. With the strangest messages imaginable. So the 1st advise is to do the clean checkout. If that fails, then do what you did - report it here. But if you can 1) indicate you did a clean checkout and when and 2) nail it down a little (for example, grep for rrdAlarm - figure out what files it's in and then check the cvs log), it helps a lot. L8tr -----Burton > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of [EMAIL PROTECTED] > Sent: Monday, May 10, 2004 2:11 AM > To: [EMAIL PROTECTED] > Subject: [ntop-dev] problems with today's cvs > > > > Burton, i think somebody over there uploaded some weird modified files on > the cvs.. please check it > > i just updated the cvs copy on my machine today, and when trying > to compile > i get this: > > (cd .libs && rm -f librrdPlugin.so && ln -s librrdPlugin-3.0.050.so > librrdPlugin.so) > ar cru .libs/librrdPlugin.a rrdPlugin.o > ranlib .libs/librrdPlugin.a > creating librrdPlugin.la > (cd .libs && rm -f librrdPlugin.la && ln -s ../librrdPlugin.la > librrdPlugin.la) > make[3]: *** No rule to make target `rrdAlarmPlugin.c', needed by > `rrdAlarmPlugin.lo'. Stop. > make[3]: Leaving directory `/kituri/kituri/ntop/cvs/ntop/plugins' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/kituri/kituri/ntop/cvs/ntop/plugins' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/kituri/kituri/ntop/cvs/ntop' > make: *** [all] Error 2 > > > this is the configure line: > ./configure --prefix=/usr/local/ntop --without-ssl --disable-ssl > --enable-de > pendency-tracking > > os: rh 73, kernel 2.4.26, all up2dates applied. > i upgraded the system rrdtool separately (1.0.48), no go... ntop uses its > own rrd not the one on the system. > > Adrian. > > _______________________________________________ > Ntop-dev mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop-dev _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
