configure: error: Installation of tclcl seems incomplete or can't be found automatica
 

hi friends,
I am trying ns2.34 on ubuntu 12.04. I used the all-in-one package. while i am typing "ns" command, "%" appears;
the tcl files are running fine along with nam.
but when i am trying to run "make" command it is giving
"make: *** No targets specified and no makefile found. Stop." error. What i found that there is no "Makefile" in ns-2.34 directory. "Makefile.in" and "Makefile.vc" is there.

i am at a loss now. could anyone help me out. Thanks in advance

Welcome to LQ.

Why would you run make, when you already have the executable 'ns' ?
.. Or could that be an `ns' from a previous ns2 build ?

? Is the file 'ns' present in ns-allinone-2.34/2.34/ :
$ ls ns-allinone-2.34/2.34/ns*

-

I tried to compile a new protocol for testing purpose on ns2.34. while i used "make myprotocol.cc" i got the error. And when I tried to run "./validate" in /ns-2.34 directory it gave the following output----

(Validation can take 1-30 hours to run.)
Mon Oct 27 00:33:04 PDT 2014
*** ./test-all-simple
Tests: tahoe1 tahoe1Bytes tahoe1RED tahoe1REDbytes tahoe2 tahoe3 tahoe3RED tahoe4 no_bug bug reno1 reno renoA reno2 reno3 reno4 reno4a reno5 reno5_nobug telnet delayed phase phase1 phase2 timers manyflows stats statsECN stats1 stats1Bytes stats1a stats1aBytes statsHeaders stats2 stats3 stats4 statsTFRC
Running test tahoe1:
../../ns test-suite-simple.tcl tahoe1 QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test tahoe1Bytes:
../../ns test-suite-simple.tcl tahoe1Bytes QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test tahoe1RED:
../../ns test-suite-simple.tcl tahoe1RED QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test tahoe1REDbytes:
../../ns test-suite-simple.tcl tahoe1REDbytes QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test tahoe2:
../../ns test-suite-simple.tcl tahoe2 QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test tahoe3:
../../ns test-suite-simple.tcl tahoe3 QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test tahoe3RED:
../../ns test-suite-simple.tcl tahoe3RED QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test tahoe4:
../../ns test-suite-simple.tcl tahoe4 QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test no_bug:
../../ns test-suite-simple.tcl no_bug QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test bug:
../../ns test-suite-simple.tcl bug QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test reno1:
../../ns test-suite-simple.tcl reno1 QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test reno:
../../ns test-suite-simple.tcl reno QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test renoA:
../../ns test-suite-simple.tcl renoA QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test reno2:
../../ns test-suite-simple.tcl reno2 QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test reno3:
../../ns test-suite-simple.tcl reno3 QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test reno4:
../../ns test-suite-simple.tcl reno4 QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test reno4a:
../../ns test-suite-simple.tcl reno4a QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test reno5:
../../ns test-suite-simple.tcl reno5 QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test reno5_nobug:
../../ns test-suite-simple.tcl reno5_nobug QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test telnet:
../../ns test-suite-simple.tcl telnet QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test delayed:
../../ns test-suite-simple.tcl delayed QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test phase:
../../ns test-suite-simple.tcl phase QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test phase1:
../../ns test-suite-simple.tcl phase1 QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test phase2:
../../ns test-suite-simple.tcl phase2 QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test timers:
../../ns test-suite-simple.tcl timers QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test manyflows:
../../ns test-suite-simple.tcl manyflows QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test stats:
../../ns test-suite-simple.tcl stats QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test statsECN:
../../ns test-suite-simple.tcl statsECN QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
Running test stats1:
../../ns test-suite-simple.tcl stats1 QUIET
./test-all-template1: 110: ./test-all-template1: ../../ns: not found
^C


COULD YOU PLEASE SUGGEST ANY SOLUTION TO THIS?

→ #3 .
Very simple : You have no executable 'ns' in ns-allinone-2.34/2.34/.

thanks a lot frnd....now please tell how to get ns in the ns-2.34 directory....and how the "%" is appearing in command prompt when typing ns ?

← #5 .
See post #2 : "".. could that be an `ns' from a previous ns2 build ?""

I.e. you can only have one file by name "ns" on your OS.
All other "ns" must be renamed to "ns_new-name".
I.e., i.e. you can have an infinite number of ns-allinone-2.xx installs
on one OS. But : Do never never add any *PATH text to .bashrc .
HOWTO : 1) $ cp ns ns-new-name 2) $ sudo cp ns-new-name /usr/local/bin/
... And then run all relevant simulations with $ ns-new-name file.tcl

Ubuntu 12.04.3, HOWTO build ns-allinone-2.34 :
$ sudo apt-get install g++-4.4
In a new folder in /home/name/ :
$ tar xvf ns-allinone-2.34.tar.gz
$ cd ns-allinone-2.34/
$ patch -p0 < otcl_ns234_gcc-4.4.patch
https://drive.google.com/file/d/0B7S...ew?usp=sharing
$ export CC=gcc-4.4 CXX=g++-4.4 && install
$ cd ns-2.34/
$ cp ns ns-new-name
$ sudo cp ns-new-name /usr/local/bin/

-

Add #6 :
? Could you have done $ sudo apt-get install ns
.... Then you will also get an extra 'ns' which can produce » % «.

YOU ARE RIGHT knudfl!!! I did that before using ns-allinone-2.34. how can I remove that now? will it create any problem? I have removed the ns related texts from the .bashrc file. still the '%' appears. is it sufficient to remove the ns-allinone-2.34 directory to remove the installed ns?

← #8 .

You can of course delete whatever you want.
But : There is no reason really to delete an "ns-allinone-2.xx".
REPEAT:
You can have an infinite number of ns-allinone-2.xx installs on one OS.
( I have about 110 different patched ns-allinone-2`s.)

You can locate the other 'ns' with $ which ns
... and then rename ns to ns-orig.
(You may need ns-orig later for running default tcl scripts :
A changed version may not be usable for tcl/ex/<examples.tcl>.)

Repeat 2 :
Renaming is the safe solution, when you have more than one ns2.

-

THANK YOU FRIEND..I HAVE INSTALLED NS-2.34, VALIDATED AND FOUND ns file in ns-2.34 directory. thanks a lot for your quick effective responses.

Dear knudfl,
I find my 'ns' file disappear from ns-2.34 directory. what should i do? re-install ns or some other process is there? all other files remain as they were, only 'ns' not found.

# 10 .
Make an install, and a backup :
$ sudo make install
( 'make install' will copy ns to /usr/local/bin/ ).
$ cp ns ns-new-name
$ sudo cp ns-new-name /usr/local/bin/

Removing the Ubuntu `ns package' : $ sudo apt-get remove ns


# 11 .
If you have no backup (Also see post #6: cp ns ns-new-name ),
.. then please run $ ./install
.. in the top directory "ns-allinone-2.34/".

-

problem in trying "MyPing" on ns2.34
 

dear knudfl,
i am trying my own ping "MyPing" on ns2.34. make is successful. myping.o created. but while running the tcl-script, it is giving the following error:

invalid command name "Agent/MyPing"
while executing
"Agent/MyPing instproc recv {from rtt} {
$self instvar node_
puts "node [$node_ id] received ping answer from \
$from with round-trip-t..."
(file "myping.tcl" line 27)

could you please suggest any solution?

← #13 .
1) Assume `myping.o' compiled into a new executable 'ns',
together with ...
2) the edited { tcl/ns-agent.tcl?, tcl/ns-default.tcl?, tcl/ns-lib.tcl },
I.e. it all depends on which code you are using.

* This "Ping example" has a "configuration file.tcl" :
. http://www.isi.edu/nsnam/ns/tutorial/nsnew.html
. http://www.isi.edu/nsnam/ns/tutorial/examples/ping.cc


P.S. : Please do not quote entire posts. A one word reference will do.

-

i took the help from the marc grei's tutorials as you mentioned. i made changes in common/packet.h, tcl/ns-default.tcl as instructed in the tutorial. but still get the error. is it needed to modify tcl/ns-agent.tcl? tcl/ns-lib.tcl? what should i write threre?