Quote:
... what about the Environment Variable ???
|
Not required on a Linux OS.
The binary 'ns' is hard coded to know where the libraries are located.
Imagine you have 2 or more versions of ns-allinone-2.xx installed :
Will make *PATH settings impossible. The ./ns command will work.
(I have up to 14 installs of different versions / different patching
on one Linux OS.)
Installing 'ns' to a system path, example :
cd ns-allinone-2.29/ns-2.29/ ; su ; make install.
The same can be done in nam-<version>/ . ( If 'nam' works.)
In order to prevent errors with the mpolsr patching, I have packed up
a new patch, with everything : ns-allinone-2.29-mpolsr-patch.tar.bz2
>
https://docs.google.com/open?id=0B7S...bjU4OFQtY2dQUQ
(10 MB: It's the most of an ns-2.29.3. An mpolsr Makefile.in is included.)
The build : tar xvf ns-allinone-2.29.3.tar.gz
&& tar xvf ns-allinone-2.29-mpolsr-patch.tar.bz2 && cd ns-allinone-2.29/
&& export CC=gcc34 CXX=g++34 && ./install
.