Re: Problem verifying ns in ns-allinone

["George F. Riley" <riley@cc.gatech.edu>]

I had the same problem, and tracked it down to using an old version
of "perl".  You mention that you have perl5.xxx in your path as did
I, but the problem is that several of the scripts reference perl as
just "exec perl", which here at Georgia Tech got an old version (v4).
I solved the problem by putting ~/ns-allinone/bin at the head of
my path, and then making a link from ~/ns-allinone/bin/perl to
the correct perl, /usr/local/bin/perl5 in our case. After that, all
validation tests ran correctly (excepting a few warnings about
some tests not being run..something about backward compatibility mode)

George
					
			-George F. Riley (riley@cc.gatech.edu)
		 	-Grad Student Liason


On Tue, 24 Feb 1998, Fang Jiang wrote:

> Hi, ns-users:
> 
> I am a new user of ns. I installed the current release ns2.1b2 using "all
> at once" at
> <http://www-mash.CS>Berkeley.EDU/ns/ns-build.html>. I got following message
> after running ./install :
> 
>    Nam has been installed successfully!
>    Please compiling your xgraph separately!
>    Ns-allinone package has been installed successfully!
>    .
>    .
>    You can run the ns validation suit with cd ns-2; ./validate
> 
> So the installation seems OK. However I encountered several problem when I
> run ./validate. The problem
> as following:
> 
>    *** ./test-all
>    tahoel tahoe2 tahoe3 tagoe4 n0_bug bug reno1 reno renoA reno2 reno3
> reno4 reno5....
>    Running tahoe1 Test output differs from reference output
>    Diagnose with: diff test-output/tahoe1.test test-output/tahoe1
>    Differences due to floating-point formatting are not significant
> 
> Then I checked tahoe1.test file and it was empty except containing title
> text and device.
> For running test tahoe2...., same problem!
> 
>    *** ./test-all-tcp
>    Tests: ecn timers timersA timers1 timers2 ... stats1
>    Running test ecn
>    ns: _o3 cleanup file5 ecn_(one_with_ecn,_one_without): syntax error in
> file ../../bin/set_flow_id at 
>    line 48, next 2 tokens "use strict"
>    syntax error in file ../../bin/set_flow_id at line 52, next 2 tokens "my("
>    Spurious backslash ignored in file ../../bin/set_flow_id at line 53.
>    syntax error in file ../../bin/set_flow_id at line 53, next 2 tokens "qw("
>    syntax error in file ../../bin/set_flow_id at line 67, next 2 tokens "my("
>    Execution of ../../bin/set_flow_id aborted due to compilation errors.
>    Can't locate 5.001000000000000334 in @INC at ../../bin/getrc line 4.
>    syntax error in file ../../bin/raw2xg at line 39, next 2 tokens "my("
>    syntax error in file ../../bin/raw2xg at line 52, next 2 tokens
> "translate_point("
>    syntax error in file ../../bin/raw2xg at line 73, next 2 tokens
> "translate_point("
>    Execution of ../../bin/raw2xg aborted due to compilation errors.
>       while executing "exec ../../bin/set_flow_id -s all.tr |
> ../../bin/getrc -s 2 -d 3 | ../../bin/raw2xg -s 
>    0.01 -m 90 -t $file > temp.rands"
>       (procedure "_o3" line 3)
>       (TestSuit finish line 3)
>       invoked from within
>    "$self finish $testname"
>       (procedure "_o3" line 11)
>       (TestSuit cleanup line 11)
>       invoked from within
>    "_o3 cleanup file5 ecn_(one_with_ecn,_one_without)"
>    Test output differs from reference output
>    Diagnose with: diff test-output-tcp/ecn.test test-output-tcp/ecn
>    Differences due to floating-point formatting are not significant
>    .
> Same problems have been encountered in running test timers and so on.
> Attached are source files getrc, set_flow_id and raw2xg. I use perl5.003 in
> my path. I am not sure if this
> causes syntax errors because source files require perl5.001? If yes,
> anybody knows where I can get these 
> source codes matched in perl5.003 or perl5.004.
> Any help will be highly appreciated.
> 
> Fang
> 
> 
>    
> 
>