[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Using NS on NT

Hello,

I seem to be having the same problems as Tan Yuan Sin. After,
I commented out the source ns-autoconf.tcl line, did a fresh
rebuild of ns-2.1b6-current, and executed my ns executable,
the contents of the files in tcl/lib are displayed, with the
following terminating lines:

		. 
		.
		.
	Simulator instproc abstract-tcp {} {
	$self instvar TahoeAckfsm_ RenoAckfsm_ TahoeDelAckfsm_
RenoDelAckfsm_ dropper_ 
	$self set TahoeAckfsm_ [new FSM/TahoeAck]
	$self set RenoAckfsm_ [new FSM/RenoAck]
	$self set TahoeDelAckfsm_ [new FSM/TahoeDelAck]
	$self set RenoDelAckfsm_ [new FSM/RenoDelAck]
	$self set nullAgent_ [new DropTargetAgent]
	}

	: invalid command name "Node/SatNode"
    	while executing
	"Node/SatNode instproc init args {
	eval $self next $args		;# parent class constructor

	$self instvar nifs_ 
	$self instvar phy_tx_ phy_rx_ mac_ ifq_ ll_..." 

I checked for ns-sat.tcl, and verified that it is sourced in my ns-lib.tcl.

It might be interesting/helpful to note after applying the same fix
below to the ns-2.1b5 version, I was able to get that version to build
and run just fine.

I appreciate your assistance,

Thanks

David Lalla


-----Original Message-----
From: Christian J�nsson [mailto:[email protected]]
Sent: Monday, August 16, 1999 3:05 PM
To: Haobo Yu; Lalla, David
Cc: [email protected]
Subject: Re: Using NS on NT


Or hand make one yourself (I did that)!

/ChJ

----- Original Message ----- 
From: Haobo Yu <[email protected]>
To: Lalla, David <[email protected]>
Cc: <[email protected]>
Sent: Monday, August 16, 1999 11:42 PM
Subject: Re: Using NS on NT


> According to an email posted by Tan Yuan Sin <[email protected]>, if you
> have 'source ns-autoconf.tcl' in tcl/lib/ns-lib.tcl, since this file is
> not available under win32 tcl2c++ will somehow mess up and generate an
> almost empty gen/ns_tcl.cc. Solution is to comment out that line in
> tcl/lib/ns-lib.tcl. 
> 
> - Haobo
>