They're all minor and easy to work around! There is some interaction/problem with automake and autoconf(?) versions...
Specifically, I'm running automake-1.5 (actually it's the RedHat automake-1.5-8.i386.rpm version). Luca seems to run 1.4 and/or 1.4-5 (which IIRC is a RedHat patched version that may be the problem child). I've seen it hinted at in other products also (do a google search on the error message), but I don't really know of an answer. What's amazing is that the google search finds something like 109 messages, from >40 different software packages! My current favorite is this extract from this http://groups.google.com/groups?hl=en&selm=handler.128486.D128486.101061958913521.ackdone%40bugs.debian.org: "this is because 'depcomp' is required for automake1.5, and nothing supports automake1.5 out of the box. That's why I don't build-conflict with it. Just use the straight 'automake' package out of testing and unstable and it'll work. (Version 1:1.4-p4-1.1). It's also peripherally because I didn't run all the necessary automake commands before packaging up this particular version of smpeg. This'll be fixed in the near future." I've been told that some versions of the gnu scripts just don't copy depcomp properly. Never really found a reference to that. You may manually need to: ln -s /usr/share/automake/depcomp depcomp (I used to have that in my copy & untar & patch from current script). However, since I'm now running 1.5, it seems to have gone away. As to the += vs =, what I've always done is to just patch the make files and run ./autogen.sh -1 I'll attach the two patch files I use (the 2nd one patches the configure files so that I can use "properly" installed versions of the library vs. ntop's private, static versions...) Note that in that patch, the change to plugins/pep/Makefile.am fails. I don't use pep so I haven't bothered fixing the patch. Also, check docs/FAQ, as this one may get you too (it's another automake/autoconf item): Q. When I compile ntop I get the following error: [...] > libtool: link: CURRENT `-release' is not a nonnegative integer > libtool: link: `-release' is not valid version information > make[2]: *** [libntop.la] Error 1 > make[2]: Leaving directory `/usr/local/src/ntop' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/usr/local/src/ntop' > make: *** [all-recursive-am] Error 2 A. It seems that some versions of GNU autoconf (> 2.13) are broken so some macros are not expanded and then the compilation fail. Workarounds: - downgrade to a stable autoconf version - edit all the ntop Makefile(s), add "0:0:0" behind any occurence of "version-info" and "2.0" behind "-release". -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of stan Sent: Monday, April 29, 2002 8:21 AM To: ntop List Subject: [Ntop] Build problems on FreeBSD STABLE I want to build an deploy ntop on Solaris 2.5.1. I'v had problems building it a while back on this platform, so I decided to give it a try agai, now thta 2.1 is close. So I downlaoded yesterdays sna[shot, and deciding to work my way up to this slowly, built it on my Debian woody system. No problem. Moving on I decided to try building it on a FreebSD STABLE syste.. That's when things went south. Here is the error I'm gatting: cd . && aclocal cd . && automake --gnu Makefile Makefile.am:62: DIST_COMMON was set with `=' and is now set with `+=' automake: configure.in: required file `./depcomp' not found gmake: *** [Makefile.in] Error 1 I figure if it won't build on this, there's no sense in even tryin Solaris 2.5.1, right? Any sugsestions as to what I may be doing wrong? -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
pvt_configure_in.patch
Description: Binary data
pvt_Makefiles.patch
Description: Binary data
