Re: [Nfdump-discuss] ft2nfdump with flow-tools-0.68 ?
netflow collecting and processing tools
Brought to you by:
phaag
From: Peter H. <pet...@sw...> - 2010-04-09 09:01:38
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There are 2 different versions of flow-tools. The one I used and which compiles is on: http://www.splintered.net/sw/flow-tools/ I guess you using the one available at Google Code. This may require some minor modification to the code. If you need it only for ft2nfdump, use the original one. Regards - Peter On 4/9/10 5:40, Ian B wrote: > I'm trying to compile nfdump 1.6.1 with ftconv enabled however I'm getting the following error: > > $ ./configure --prefix=/usr/local/nfdump-1.6.1 --enable-ftconv --enable-nfprofile --with-ftpath=/usr/local/flow-tools/ > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking for style of include used by make... GNU > checking dependency style of gcc... gcc3 > checking whether gcc and cc understand -c and -o together... yes > checking whether we are using SunPro C... no > checking for bison... no > checking for byacc... byacc > checking for flex... flex > checking lex output file root... lex.yy > checking lex library... -lfl > checking whether yytext is a pointer... yes > checking for a BSD-compatible install... /usr/bin/install -c > checking for zlibVersion in -lz... yes > configure: error: ftlib.h file not found in flow-tools directory '/usr/local/flow-tools/'. Use --with-ftpath=PATH > > > I checked 'configure' and it appears to be looking in '/lib' for ftlib.h however I'm using flow-tools-0.68 which puts that in '/include' by default... > > If I modify 'configure' to look in the correct location for ftlib.h then it completes OK, however make barfs with: > > gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/local/flow-tools//src -I/usr/local/flow-tools//lib -g -O2 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wmissing-noreturn -MT ft2nfdump-ft2nfdump.o -MD -MP -MF .deps/ft2nfdump-ft2nfdump.Tpo -c -o ft2nfdump-ft2nfdump.o `test -f 'ft2nfdump.c' || echo './'`ft2nfdump.c > ft2nfdump.c:71:21: error: ftbuild.h: No such file or directory > make[3]: *** [ft2nfdump-ft2nfdump.o] Error 1 > > > ftbuild.h appears to be missing from flow-tools-0.68 :( > > Is it possible to compile ft2nfdump agains flow-tools-0.68 or do I need to look at using an older version of flow-tools? > > Thanks, > Ian. > > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Nfdump-discuss mailing list > Nfd...@li... > https://lists.sourceforge.net/lists/listinfo/nfdump-discuss - -- _______ SWITCH - The Swiss Education and Research Network ______ Peter Haag, Security Engineer, Member of SWITCH CERT PGP fingerprint: D9 31 D5 83 03 95 68 BA FB 84 CA 94 AB FC 5D D7 SWITCH, Werdstrasse 2, P.O. Box, CH-8021 Zurich, Switzerland E-mail: pet...@sw... Web: http://www.switch.ch/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBS77s6P5AbZRALNr/AQKPsAP/QdM8fWUz6wGCee2cREbf9U+Yr6GAQAEE hI+ixYaczFQfn5g7hydlemDdNiB1mTrAyB0TDtOYX9LIjZCpwwKB/l7hXkaRV2Mf LV7Q4idyla+0bLqDyk83rhuUo3SieYHYctkmZjGYNPyBe2aSGpTGPX2uOhz6RhQm G1K3G8rG/rc= =h8ep -----END PGP SIGNATURE----- |