tcptrace-bugs Compile Problem + ns2 support

From: Ahmad Khayyat (ahmad.khayyat@ece.queensu.ca)
Date: 02/21/06 

Message-ID: <43FB41EC.1090703@ece.queensu.ca>
Date: Tue, 21 Feb 2006 11:38:04 -0500
From: Ahmad Khayyat <ahmad.khayyat@ece.queensu.ca>
Subject: tcptrace-bugs Compile Problem + ns2 support

Hi,

I was trying to use tcptrace to analyze ns2 trace files, but was getting
(among other output):

Checking for file format 'ns' (ns -- network simulator from LBL)
File format is NOT 'ns'

when I run "tcptrace -d <filename.tr>"

I was using tcptrace version 6.6.1-1 from debian testing.

Before complaining, I decided to check out the latest version. I
downloaded tcptrace 6.6.7 and did a "./configure" and then a "make", but
unfortunately, "make" did not complete. It gives the following error
while compiling the file "filt_scanner.c":

./filt_scanner.l: In function 'filtyywrap':
./filt_scanner.l:159: error: 'yytext_ptr' undeclared (first use in this
function)
./filt_scanner.l:159: error: (Each undeclared identifier is reported
only once
./filt_scanner.l:159: error: for each function it appears in.)
make: *** [filt_scanner.o] Error 1

Here is my "./configure" output (config.log is attached):

./configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
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 executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking gcc version... 4
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking whether make sets ${MAKE}... yes
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 bison... bison -y
checking for main in -lm... yes
checking how to run the C preprocessor... gcc -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 for unsigned long long int... yes
checking size of unsigned long long int... 8
checking for unsigned long int... yes
checking size of unsigned long int... 4
checking for unsigned int... yes
checking size of unsigned int... 4
checking for unsigned short... yes
checking size of unsigned short... 2
checking for gethostbyname... yes
checking for socket... yes
checking for putmsg in -lstr... no
checking for fpurge... no
checking for mkstemp... yes
checking for valloc... yes
checking for memalign... yes
checking for inet_pton... yes
checking how to print unsigned long long... %llu
configure: creating ./config.status
config.status: creating Makefile

Please let me know if you need any further info. to diagnose the problem.

One more question, should tcptrace be able to read ns2 trace files
directly or do I still need to apply a patch? I realize I have to
separate sender from receiver events and run tcptrace on each alone, but
do I need to do anything else to be able to analyze ns2 trace files
using tcptrace?

Thanks in advance..

Regards,
- Ahmad Khayyat

This archive was generated by hypermail 2.1.7 : 02/21/06 EST