Re: I am sorry that I do not know how to start ns2.

[Zhenhai Duan <duan@cs.umn.edu>]

I did not run into this problem before, so I do not know the answer for
sure. What I can tell is that: Because the nam(maybe also ns) is
compilered with dynamic lib, so when you run it, it will search for the
corresponding dynamic libs. It sounds that you have compiled nam
correctly, but it can not find otcl lib, so you may give a try to add
the directory where libotcl.so sits to the LIB search path.

Good Luck.
--Zhenhai
=============================================
On Sun, 25 Jan 1998, K Sun wrote:

> Hi,
>     Thank you very much. I added the "-ldl" in the appropriate 
> place in the Makefile. It seems there are some progressed, but 
> there is still a fault. I do not know why.
>     Before I added "-ldl",  I tried to "make". It did not work.
>      After I added the "-ldl", I try it again. Yes, it looks good. I 
> can "make" it smoothly.
> 
>      But when I run it, there was still a fault, although this time, it 
> did not report something wrong wtih libtcl80.... :
> 
> "./nam-1.0a6: error in loading shared libraries
>   libotcl.so can not open shared object file: No such file or directory"
> 
>   So, I review the Makefile of "nam". I find, yes, in the "LIB=..".
> there are words like "../otcl -lotcl". And in the directory "otcl", 
> there is the file "libotcl.so". It makes me more confusing.
>    By the way, I have re-completed "configure, make, make install" otcl.
> So, in the directory /usr/local/lib, there is also the file 
> "libotcl.so".
> Perhaps, I should add "/usr/local/lib -loctl" in the Makefile?
> 
>    What is wrong with my installation and runing? 
>    Really hope your further help.
> 
>    Best wishes,
> 
>     Sun Kai 
> 
> On Sun, 24 Jan 1999 20:09:34 -0600 (CST) Zhenhai Duan <duan@cs.umn.edu> 
> wrote:
> 
> > If you are installing all-in-one on Linux, and did not find nam, As
> > mentioned in the nam FAQ, the problem may be:
> > 
> > Problem: Nam gets link errors when building with references to "dlopen"
> >     similar functions beginning with dl. (This problem also occurs with
> > 	ns.) 
> > 
> >     Work-around: You need to manually add the library for dynamic linking
> >     to ns's Makefile. Look in the Makefile for the line LIB= and add your
> >     systems library for dynamic linking (typically -ldl). 
> > 
> > So, You need to manually make nam after you modified Makefile under nam/
> > to add in -ldl.
> > 
> > Also please visit:
> > 	http://www-mash.CS.Berkeley.EDU/nam/nam-problems.html
> > 
> > Good Luck.
> > --Zhenhai
> > ----------------------------------------------------------
> > On Sat, 24 Jan 1998, K Sun wrote:
> > 
> > > Hello, there,
> > >        Thanks. However, I still have problems.
> > > I download the nam-1.0a6 (binary release) for Linux.
> > > When I try to run it, there is some mistakes:
> > > 
> > > ....
> > > ./nam-1.0a6: error in loading shared libraries
> > > /usr/lib/libtcl8.0.so: undefined symbol:stat
> > > .......
> > > 
> > >    I thought, perhaps, it was because I did not correctly install TCL 
> > > package. So, I specially re-install the TCL8.0. However, after I 
> > > installed TCL 8.0 and run nam-1.0a6, there's the same fault.
> > > I do not know why. Perhaps, there is something wrong with TCL packages?
> > > 
> > > really hope further reply.
> > > 
> > >     Best Regards,
> > > 
> > >     Sincerely Yours,
> > > 
> > >                       Sun Kai
> > > 
> > > On Sun, 24 Jan 1999 15:43:51 -0500 (EST) Sukesh Garg 
> > > <sukeshgg@caip.rutgers.edu> wrote:
> > > 
> > > > 
> > > > 
> > > > > Hello,
> > > > >     Thank you previous help.
> > > > > The Marc Greis's tutorial is really a good guide for me.
> > > > > However,when I try the first example, I meet a problem.
> > > > > >From the text of the first tcl script, I feel there should be an 
> > > > > execute file "nam". Nevertheless, I can not find it in any directorys.
> > > > 
> > > > nam is also available as a self extracting binary... check it at:
> > > > 
> > > > http://www-mash.cs.berkeley.edu/nam/
> > > > 
> > > > 
> > > > 
> > > > > There is only a directory name "nam" under the directory "ns-2".
> > > > > I do not know whether the above fact means I have not installed nam 
> > > > > successfully since validate only checks ns-2 simulator.
> > > > 
> > > > well nam is a complete package.......not part of ns...
> > > > 
> > > > >     What I downloaded and installed is ns-allinone-2.1b4a.
> > > > >     By the way, what is the difference between nam.1 and nam?
> > > > > 
> > > > > 
> > > > 
> > > > ns-allinone-2.1b4a is not recoed for wins... 
> > > > 
> > > > nam.1 is documentation for nam
> > > > nam is the exe for it...
> > > > 
> > > > I recomend intalling the binaries and giving including it in ypour path
> > > > 
> > > > HTH
> > > > Sukesh
> > > 
> > > 
> > > 
> 
> 
>