From sking at kingrst.com Sun Jul 11 21:09:42 2010 From: sking at kingrst.com (Steven King) Date: Sun Jul 11 21:09:51 2010 Subject: [Flow-tools] Compilation Error on Slackware Message-ID: <4C3A6B56.4060204@kingrst.com> Hello, I am attempting to compile flow-tools on Slackware 13.1 64bit. I downloaded the 0.66 source code and ran configure with no options, and make. The configure completes fine (from what I can tell) however the make fails. I have included the output of configure and the make command. If anyone could provide any assistance I would greatly appreciate it. root@host2:~/flow-tools-0.66# ./configure checking for a BSD-compatible install... /usr/bin/ginstall -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output... 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 ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for a BSD-compatible install... /usr/bin/ginstall -c checking whether make sets $(MAKE)... (cached) yes checking for bison... bison -y checking for ranlib... ranlib checking for flex... flex checking for yywrap in -lfl... yes checking lex output file root... lex.yy checking whether yytext is a pointer... yes checking for main in -ly... yes checking for zlibVersion in -lz... yes checking for allow_severity in -lwrap... yes checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking features.h usability... yes checking features.h presence... yes checking for features.h... yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking malloc.h usability... yes checking malloc.h presence... yes checking for malloc.h... yes checking for string.h... (cached) yes checking for strings.h... (cached) yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking syslog.h usability... yes checking syslog.h presence... yes checking for syslog.h... yes checking for unistd.h... (cached) yes checking for sin_len in sockaddr_in ... no checking for an ANSI C-conforming const... yes checking for off_t... yes checking for pid_t... yes checking for size_t... yes checking for struct stat.st_rdev... yes checking whether time.h and sys/time.h may both be included... yes checking whether struct tm is in sys/time.h or time.h... time.h checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... yes checking for working alloca.h... yes checking for alloca... yes checking return type of signal handlers... void checking for gethostbyname in -lnsl... yes checking for socket in -lsocket... no checking for gethostname... yes checking for gettimeofday... yes checking for select... yes checking for socket... yes checking for strdup... yes checking for strtoul... yes checking for timelocal... yes checking for sigaction... yes checking for strsep... yes checking for strerror... yes checking for strtoull... yes checking strtoul returns 64 bits... yes configure: creating ./config.status config.status: creating lib/Makefile config.status: creating src/Makefile config.status: creating Makefile config.status: creating docs/Makefile config.status: creating lib/ftpaths.h config.status: creating configs/Makefile config.status: creating docs/flow-capture.1 config.status: creating docs/flow-capture.html config.status: creating docs/flow-nfilter.1 config.status: creating docs/flow-nfilter.html config.status: creating docs/flow-print.1 config.status: creating docs/flow-print.html config.status: creating docs/flow-report.1 config.status: creating docs/flow-report.html config.status: creating docs/flow-receive.1 config.status: creating docs/flow-receive.html config.status: creating docs/flow-tag.1 config.status: creating docs/flow-tag.html config.status: creating docs/flow-mask.1 config.status: creating docs/flow-mask.html config.status: creating docs/flow-fanout.1 config.status: creating docs/flow-fanout.html config.status: creating lib/ftconfig.h config.status: executing depfiles commands Please subscribe to the flow-tools mailing list by sending a message to flow-tools-request@splintered.net Now type make to continue the build process root@host2:~/flow-tools-0.66# make Making all in lib make[1]: Entering directory `/root/flow-tools-0.66/lib' make all-am make[2]: Entering directory `/root/flow-tools-0.66/lib' if gcc -I. -I./lib -I. -I. -I. -g -Wall -g -Wall -MT ftio.o -MD -MP -MF ".deps/ftio.Tpo" \ -c -o ftio.o `test -f 'ftio.c' || echo './'`ftio.c; \ then mv ".deps/ftio.Tpo" ".deps/ftio.Po"; \ else rm -f ".deps/ftio.Tpo"; exit 1; \ fi ftio.c: In function 'readn': ftio.c:2270: error: lvalue required as left operand of assignment ftio.c: In function 'writen': ftio.c:2295: error: lvalue required as left operand of assignment make[2]: *** [ftio.o] Error 1 make[2]: Leaving directory `/root/flow-tools-0.66/lib' make[1]: *** [all] Error 2 make[1]: Leaving directory `/root/flow-tools-0.66/lib' make: *** [all-recursive] Error 1 -- Steve King Senior Linux Engineer - Advance Internet, Inc. Cisco Certified Network Associate CompTIA Linux+ Certified Professional CompTIA A+ Certified Professional From sking at kingrst.com Sun Jul 11 21:41:29 2010 From: sking at kingrst.com (Steven King) Date: Sun Jul 11 21:41:38 2010 Subject: [Flow-tools] Compilation Error on Slackware In-Reply-To: <1278898586.3079.1.camel@endor-jr.in.novare.com.hk> References: <4C3A6B56.4060204@kingrst.com> <1278898586.3079.1.camel@endor-jr.in.novare.com.hk> Message-ID: <4C3A72C9.60802@kingrst.com> Thanks William, I will check out the patch. I tried 0.68 as well. Same error, but I figured I'd email about the stable version first. I will let you know how the patch works out. On 7/11/10 9:36 PM, William Emmanuel Yu wrote: > Looks like a GCC 4 issue. Please check out this patch: > http://cng.ateneo.net/cng/wyu/software/patch/flow-tools-0.68-gcc4.patch > > Also try using the latest flow-tools. > > On Sun, 2010-07-11 at 21:09 -0400, Steven King wrote: >> Hello, >> >> I am attempting to compile flow-tools on Slackware 13.1 64bit. I >> downloaded the 0.66 source code and ran configure with no options, and >> make. The configure completes fine (from what I can tell) however the >> make fails. >> >> I have included the output of configure and the make command. If anyone >> could provide any assistance I would greatly appreciate it. >> >> root@host2:~/flow-tools-0.66# ./configure >> checking for a BSD-compatible install... /usr/bin/ginstall -c >> checking whether build environment is sane... yes >> checking for gawk... gawk >> checking whether make sets $(MAKE)... yes >> checking for gcc... gcc >> checking for C compiler default output... 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 ANSI C... none needed >> checking for style of include used by make... GNU >> checking dependency style of gcc... gcc3 >> checking for a BSD-compatible install... /usr/bin/ginstall -c >> checking whether make sets $(MAKE)... (cached) yes >> checking for bison... bison -y >> checking for ranlib... ranlib >> checking for flex... flex >> checking for yywrap in -lfl... yes >> checking lex output file root... lex.yy >> checking whether yytext is a pointer... yes >> checking for main in -ly... yes >> checking for zlibVersion in -lz... yes >> checking for allow_severity in -lwrap... yes >> checking for dirent.h that defines DIR... yes >> checking for library containing opendir... none required >> checking how to run the C preprocessor... gcc -E >> checking for egrep... grep -E >> checking for ANSI C header files... yes >> checking for sys/types.h... yes >> checking for sys/stat.h... yes >> checking for stdlib.h... yes >> checking for string.h... yes >> checking for memory.h... yes >> checking for strings.h... yes >> checking for inttypes.h... yes >> checking for stdint.h... yes >> checking for unistd.h... yes >> checking fcntl.h usability... yes >> checking fcntl.h presence... yes >> checking for fcntl.h... yes >> checking features.h usability... yes >> checking features.h presence... yes >> checking for features.h... yes >> checking limits.h usability... yes >> checking limits.h presence... yes >> checking for limits.h... yes >> checking malloc.h usability... yes >> checking malloc.h presence... yes >> checking for malloc.h... yes >> checking for string.h... (cached) yes >> checking for strings.h... (cached) yes >> checking sys/time.h usability... yes >> checking sys/time.h presence... yes >> checking for sys/time.h... yes >> checking syslog.h usability... yes >> checking syslog.h presence... yes >> checking for syslog.h... yes >> checking for unistd.h... (cached) yes >> checking for sin_len in sockaddr_in ... >> no >> checking for an ANSI C-conforming const... yes >> checking for off_t... yes >> checking for pid_t... yes >> checking for size_t... yes >> checking for struct stat.st_rdev... yes >> checking whether time.h and sys/time.h may both be included... yes >> checking whether struct tm is in sys/time.h or time.h... time.h >> checking for stdlib.h... (cached) yes >> checking for unistd.h... (cached) yes >> checking for getpagesize... yes >> checking for working mmap... yes >> checking for working alloca.h... yes >> checking for alloca... yes >> checking return type of signal handlers... void >> checking for gethostbyname in -lnsl... yes >> checking for socket in -lsocket... no >> checking for gethostname... yes >> checking for gettimeofday... yes >> checking for select... yes >> checking for socket... yes >> checking for strdup... yes >> checking for strtoul... yes >> checking for timelocal... yes >> checking for sigaction... yes >> checking for strsep... yes >> checking for strerror... yes >> checking for strtoull... yes >> checking strtoul returns 64 bits... yes >> configure: creating ./config.status >> config.status: creating lib/Makefile >> config.status: creating src/Makefile >> config.status: creating Makefile >> config.status: creating docs/Makefile >> config.status: creating lib/ftpaths.h >> config.status: creating configs/Makefile >> config.status: creating docs/flow-capture.1 >> config.status: creating docs/flow-capture.html >> config.status: creating docs/flow-nfilter.1 >> config.status: creating docs/flow-nfilter.html >> config.status: creating docs/flow-print.1 >> config.status: creating docs/flow-print.html >> config.status: creating docs/flow-report.1 >> config.status: creating docs/flow-report.html >> config.status: creating docs/flow-receive.1 >> config.status: creating docs/flow-receive.html >> config.status: creating docs/flow-tag.1 >> config.status: creating docs/flow-tag.html >> config.status: creating docs/flow-mask.1 >> config.status: creating docs/flow-mask.html >> config.status: creating docs/flow-fanout.1 >> config.status: creating docs/flow-fanout.html >> config.status: creating lib/ftconfig.h >> config.status: executing depfiles commands >> >> Please subscribe to the flow-tools mailing list by sending a message to >> flow-tools-request@splintered.net >> >> Now type make to continue the build process >> >> root@host2:~/flow-tools-0.66# make >> Making all in lib >> make[1]: Entering directory `/root/flow-tools-0.66/lib' >> make all-am >> make[2]: Entering directory `/root/flow-tools-0.66/lib' >> if gcc -I. -I./lib -I. -I. -I. -g -Wall -g -Wall -MT ftio.o -MD -MP >> -MF ".deps/ftio.Tpo" \ >> -c -o ftio.o `test -f 'ftio.c' || echo './'`ftio.c; \ >> then mv ".deps/ftio.Tpo" ".deps/ftio.Po"; \ >> else rm -f ".deps/ftio.Tpo"; exit 1; \ >> fi >> ftio.c: In function 'readn': >> ftio.c:2270: error: lvalue required as left operand of assignment >> ftio.c: In function 'writen': >> ftio.c:2295: error: lvalue required as left operand of assignment >> make[2]: *** [ftio.o] Error 1 >> make[2]: Leaving directory `/root/flow-tools-0.66/lib' >> make[1]: *** [all] Error 2 >> make[1]: Leaving directory `/root/flow-tools-0.66/lib' >> make: *** [all-recursive] Error 1 >> -- Steve King Senior Linux Engineer - Advance Internet, Inc. Cisco Certified Network Associate CompTIA Linux+ Certified Professional CompTIA A+ Certified Professional From sking at kingrst.com Sun Jul 11 21:54:10 2010 From: sking at kingrst.com (Steven King) Date: Sun Jul 11 21:54:16 2010 Subject: [Flow-tools] Compilation Error on Slackware In-Reply-To: <4C3A72C9.60802@kingrst.com> References: <4C3A6B56.4060204@kingrst.com> <1278898586.3079.1.camel@endor-jr.in.novare.com.hk> <4C3A72C9.60802@kingrst.com> Message-ID: <4C3A75C2.5070807@kingrst.com> The patch file and 0.68 worked well. Thanks for your help! On 7/11/10 9:41 PM, Steven King wrote: > Thanks William, > > I will check out the patch. I tried 0.68 as well. Same error, but I > figured I'd email about the stable version first. I will let you know > how the patch works out. > > On 7/11/10 9:36 PM, William Emmanuel Yu wrote: >> Looks like a GCC 4 issue. Please check out this patch: >> http://cng.ateneo.net/cng/wyu/software/patch/flow-tools-0.68-gcc4.patch >> >> Also try using the latest flow-tools. >> >> On Sun, 2010-07-11 at 21:09 -0400, Steven King wrote: >>> Hello, >>> >>> I am attempting to compile flow-tools on Slackware 13.1 64bit. I >>> downloaded the 0.66 source code and ran configure with no options, and >>> make. The configure completes fine (from what I can tell) however the >>> make fails. >>> >>> I have included the output of configure and the make command. If anyone >>> could provide any assistance I would greatly appreciate it. >>> >>> root@host2:~/flow-tools-0.66# ./configure >>> checking for a BSD-compatible install... /usr/bin/ginstall -c >>> checking whether build environment is sane... yes >>> checking for gawk... gawk >>> checking whether make sets $(MAKE)... yes >>> checking for gcc... gcc >>> checking for C compiler default output... 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 ANSI C... none needed >>> checking for style of include used by make... GNU >>> checking dependency style of gcc... gcc3 >>> checking for a BSD-compatible install... /usr/bin/ginstall -c >>> checking whether make sets $(MAKE)... (cached) yes >>> checking for bison... bison -y >>> checking for ranlib... ranlib >>> checking for flex... flex >>> checking for yywrap in -lfl... yes >>> checking lex output file root... lex.yy >>> checking whether yytext is a pointer... yes >>> checking for main in -ly... yes >>> checking for zlibVersion in -lz... yes >>> checking for allow_severity in -lwrap... yes >>> checking for dirent.h that defines DIR... yes >>> checking for library containing opendir... none required >>> checking how to run the C preprocessor... gcc -E >>> checking for egrep... grep -E >>> checking for ANSI C header files... yes >>> checking for sys/types.h... yes >>> checking for sys/stat.h... yes >>> checking for stdlib.h... yes >>> checking for string.h... yes >>> checking for memory.h... yes >>> checking for strings.h... yes >>> checking for inttypes.h... yes >>> checking for stdint.h... yes >>> checking for unistd.h... yes >>> checking fcntl.h usability... yes >>> checking fcntl.h presence... yes >>> checking for fcntl.h... yes >>> checking features.h usability... yes >>> checking features.h presence... yes >>> checking for features.h... yes >>> checking limits.h usability... yes >>> checking limits.h presence... yes >>> checking for limits.h... yes >>> checking malloc.h usability... yes >>> checking malloc.h presence... yes >>> checking for malloc.h... yes >>> checking for string.h... (cached) yes >>> checking for strings.h... (cached) yes >>> checking sys/time.h usability... yes >>> checking sys/time.h presence... yes >>> checking for sys/time.h... yes >>> checking syslog.h usability... yes >>> checking syslog.h presence... yes >>> checking for syslog.h... yes >>> checking for unistd.h... (cached) yes >>> checking for sin_len in sockaddr_in ... >>> no >>> checking for an ANSI C-conforming const... yes >>> checking for off_t... yes >>> checking for pid_t... yes >>> checking for size_t... yes >>> checking for struct stat.st_rdev... yes >>> checking whether time.h and sys/time.h may both be included... yes >>> checking whether struct tm is in sys/time.h or time.h... time.h >>> checking for stdlib.h... (cached) yes >>> checking for unistd.h... (cached) yes >>> checking for getpagesize... yes >>> checking for working mmap... yes >>> checking for working alloca.h... yes >>> checking for alloca... yes >>> checking return type of signal handlers... void >>> checking for gethostbyname in -lnsl... yes >>> checking for socket in -lsocket... no >>> checking for gethostname... yes >>> checking for gettimeofday... yes >>> checking for select... yes >>> checking for socket... yes >>> checking for strdup... yes >>> checking for strtoul... yes >>> checking for timelocal... yes >>> checking for sigaction... yes >>> checking for strsep... yes >>> checking for strerror... yes >>> checking for strtoull... yes >>> checking strtoul returns 64 bits... yes >>> configure: creating ./config.status >>> config.status: creating lib/Makefile >>> config.status: creating src/Makefile >>> config.status: creating Makefile >>> config.status: creating docs/Makefile >>> config.status: creating lib/ftpaths.h >>> config.status: creating configs/Makefile >>> config.status: creating docs/flow-capture.1 >>> config.status: creating docs/flow-capture.html >>> config.status: creating docs/flow-nfilter.1 >>> config.status: creating docs/flow-nfilter.html >>> config.status: creating docs/flow-print.1 >>> config.status: creating docs/flow-print.html >>> config.status: creating docs/flow-report.1 >>> config.status: creating docs/flow-report.html >>> config.status: creating docs/flow-receive.1 >>> config.status: creating docs/flow-receive.html >>> config.status: creating docs/flow-tag.1 >>> config.status: creating docs/flow-tag.html >>> config.status: creating docs/flow-mask.1 >>> config.status: creating docs/flow-mask.html >>> config.status: creating docs/flow-fanout.1 >>> config.status: creating docs/flow-fanout.html >>> config.status: creating lib/ftconfig.h >>> config.status: executing depfiles commands >>> >>> Please subscribe to the flow-tools mailing list by sending a message to >>> flow-tools-request@splintered.net >>> >>> Now type make to continue the build process >>> >>> root@host2:~/flow-tools-0.66# make >>> Making all in lib >>> make[1]: Entering directory `/root/flow-tools-0.66/lib' >>> make all-am >>> make[2]: Entering directory `/root/flow-tools-0.66/lib' >>> if gcc -I. -I./lib -I. -I. -I. -g -Wall -g -Wall -MT ftio.o -MD -MP >>> -MF ".deps/ftio.Tpo" \ >>> -c -o ftio.o `test -f 'ftio.c' || echo './'`ftio.c; \ >>> then mv ".deps/ftio.Tpo" ".deps/ftio.Po"; \ >>> else rm -f ".deps/ftio.Tpo"; exit 1; \ >>> fi >>> ftio.c: In function 'readn': >>> ftio.c:2270: error: lvalue required as left operand of assignment >>> ftio.c: In function 'writen': >>> ftio.c:2295: error: lvalue required as left operand of assignment >>> make[2]: *** [ftio.o] Error 1 >>> make[2]: Leaving directory `/root/flow-tools-0.66/lib' >>> make[1]: *** [all] Error 2 >>> make[1]: Leaving directory `/root/flow-tools-0.66/lib' >>> make: *** [all-recursive] Error 1 >>> -- Steve King Senior Linux Engineer - Advance Internet, Inc. Cisco Certified Network Associate CompTIA Linux+ Certified Professional CompTIA A+ Certified Professional From jones at tacc.utexas.edu Mon Jul 12 11:10:34 2010 From: jones at tacc.utexas.edu (William Jones) Date: Mon Jul 12 11:10:39 2010 Subject: FW: [Flow-tools] error while installing flowtool-0.68 Message-ID: Try this version. -----Original Message----- From: flow-tools-bounces@list.splintered.net [mailto:flow-tools-bounces@list.splintered.net] On Behalf Of Ed Ravin Sent: Thursday, June 03, 2010 2:30 PM To: hardik thakar Cc: Flow-tools@list.splintered.net Subject: Re: [Flow-tools] error while installing flowtool-0.68 On Thu, Jun 03, 2010 at 12:40:51PM -0000, hardik thakar wrote: > r/s > pl guide me for the attached file error when installing on linux > platform > regards > hardik Hardik, try the most recent fork of flow-tools at: http://code.google.com/p/flow-tools/ This version has several bug fixes and improvements, including portability fixes. The 0.68 version at splintered.net is no longer current. _______________________________________________ Flow-tools mailing list flow-tools@splintered.net http://mailman.splintered.net/mailman/listinfo/flow-tools From sscholz at ikr.uni-stuttgart.de Tue Jul 13 04:44:37 2010 From: sscholz at ikr.uni-stuttgart.de (Sebastian Scholz) Date: Tue Jul 13 04:44:40 2010 Subject: [Flow-tools] difference in the file format used by flow-capture and the other tools? Message-ID: <201007131044.37920.sscholz@ikr.uni-stuttgart.de> Hello, I have written my own reader for flow-tools files in Java. It works quiet good, but not in the case if I want to read compressed files that are generated by flow-capture, because the compression seems to be corrupted for the Java inflater. Only after processing the files with flow-split or flow-filter I'm able to read them in, even if they are still compressed. Is there a difference in the file format used by flow-capture and the other tools? With my limited C knowledge I wasn't able to find a difference in the code. Thanks Sebastian -- ------------------------------------------------------------------- Sebastian Scholz Institute of Communication Networks and Computer Engineering (IKR) University of Stuttgart Pfaffenwaldring 47, 70569 Stuttgart, Germany -------------------------------------------------------------------