[ndnSIM] New Ubuntu machine - new bizarre errors

Tue Jan 3 22:38:07 PST 2017

2.3 should be ok.  Which exactly repository you cloned for scenario-template?  I just checked with the one listed on ndnSIM website (https://github.com/named-data-ndnSIM/scenario-template.git <https://github.com/named-data-ndnSIM/scenario-template.git>) and everything is working.

The correct template repository should not have this check:

     ...
     Checking for 'libndn-cxx'                : not found
     ...

The you should have directory structure something like this

some-folder-for-simulations/
├── ns-3/
│   ├── ...
│   ├── src/
│   │   ├── ...
│   │   ├── ndnSIM/
│   │   │   ├── ndn-cxx/
│   │   │   ├── NFD/
│   │   │   ├── model/
│   │   │   ├── ...
│   │   ├── ...
│   ├── ...
├── pybindgen/
│   ├── ...
└── scenario/
    ├── README.md
    ├── extensions/
    │   ├── README.md
    │   ├── some-code.hpp
    │   └── some-code.cpp
    ├── graphs/
    │   ├── ...
    ├── results/
    ├── run.py
    ├── scenarios/
    │   ├── README.md
    │   └── scenario-name.cpp
    ├── waf
    └── wscript

When you're inside scenario/ folder, you can run `./waf --run scenario-name` (files in scenarios/ folder are getting compiled into individual scenarios).

---
Alex

> On Jan 3, 2017, at 9:56 PM, John Baugh <jpbaugh at umich.edu> wrote:
> 
> Junxiao,
> 
> That is peculiar...  perhaps I should ask a different question:
> 
> Should I be using ndnSIM 2.3, even?  Or should I just go back to 2.1?
> 
> If so, how might I accomplish this to ensure I don't get the newest version?
> 
> Thanks,
> 
> John
> 
> On Wed, Jan 4, 2017 at 12:51 AM, Junxiao Shi <shijunxiao at email.arizona.edu <mailto:shijunxiao at email.arizona.edu>> wrote:
> Hi John
> 
> The scenario template, as of commit 2b5b6f55f04982273e62127082a19459ec68ff43 <https://github.com/named-data-ndnSIM/scenario-template/tree/2b5b6f55f04982273e62127082a19459ec68ff43> , is compatible with ndnSIM 2.1, and may or may not work with other versions.
> However, I do not see why the scenario template is looking for ndn-cxx, because there's no "ndn-cxx" token in its wscript.
> 
> Yours, Junxiao
> 
> On Tue, Jan 3, 2017 at 10:44 PM, John Baugh <jpbaugh at umich.edu <mailto:jpbaugh at umich.edu>> wrote:
> Junxiao,
> 
> By "./waf configure and ./waf inside the scenario template", I took that as the ./waf inside my my-simulations directory, correct?
> 
> I performed the ./waf configure from inside there after doing a ./waf install (from inside ns-3 directory), and I get the following:
> 
> jpbaugh at Janeway:~/ndnSIM/my-simulations$ ./waf configure
> Setting top to                           : /home/jpbaugh/ndnSIM/my-simulations
> Setting out to                           : /home/jpbaugh/ndnSIM/my-simulations/build
> Checking for 'gcc' (C compiler)          : /usr/bin/gcc
> Checking for 'g++' (C++ compiler)        : /usr/bin/g++
> Checking supported CXXFLAGS              : -std=c++11
> Checking supported CXXFLAGS              : -pedantic -Wall -O2 -g
> Checking for program 'pkg-config'        : /usr/bin/pkg-config
> Checking for 'libndn-cxx'                : not found
> The configuration failed
> (complete log in /home/jpbaugh/ndnSIM/my-simulations/build/config.log)
> 
> 
> My obvious assumption is that it cannot find the ndn-cxx library.  But I am following the instructions by the letter.  This is a fresh computer and a fresh install, so what might be the issue here?  And what is the best / appropriate corrective measure, as I assume ndnSIM is already installed.
> 
> Thanks,
> 
> John
> 
> On Wed, Jan 4, 2017 at 12:36 AM, Junxiao Shi <shijunxiao at email.arizona.edu <mailto:shijunxiao at email.arizona.edu>> wrote:
> Hi John
> 
> 1.)  Since I already had installed ndnSIM using the instructions in Getting Started on the main ndnSIM.net page, I don't have to perform another git clone on ns-3-dev-ndnSIM.git or any of those files right?  It seems it's just downloading a separate copy of ndnSIM to put in a separate directory.  So, all I did per the instructions was a git clone on the ndnSIM-scenario-template-git.
> You don't need to clone ns-3 or ndnSIM again, as long as you have compatible version.
> 
> 2.)  I placed the downloaded branch (terminology might be off here) in my-simulations, which in turn I have inside the ndnSIM folder.  So, my-simulations is a directory that is a sibling directory of ns-3 and pybindgen, all three being inside the top level ndnSIM folder.  Is this correct / ok?
> Yes, this is correct. scenario template must be outside of ns-3 folder.
> 
> 3.)  I am very confused about the difference between the extensions and scenarios directories.  I was under the impression I could put a subdirectory under extensions named as my scenario, so I named a subdirectory of extensions "jpb-strategy1-test", which contains jpb-strategy1.cpp and a umd/ directory with some classes I'm using (they worked fine with ndnSIM 2.1.)  Is this correct?
> You may place multiple files in extensions/ folder, which will be linked with every scenario.
> Every file in scenarios/ folder is an individual simulation which must have a main() function. Every file is linked with every object from extensions/ to create an executable.
> 
> 4.)  Now, it cannot find the scenario, regardless of whether its inside extensions or scenarios.  Does a .cpp or .cc file have to be at the top level or can I put a subdirectory?  I just want to remain organized.  I get the following:
> 
> jpbaugh at Janeway:~/ndnSIM/ns-3$ ./waf --run=jpb-strategy1-test
> Waf: Entering directory `/home/jpbaugh/ndnSIM/ns-3/build'
> program 'jpb-strategy1-test' not found; available programs are: ['subdir', 'scratch/subdir/subdir', 'scratch-simulator', 'scratch/scratch-simulator', 'test-runner', 'utils/test-runner', 'bench-simulator', 'utils/bench-simulator', 'bench-packets', 'utils/bench-packets', 'print-introspected-doxygen', 'utils/print-introspected-doxygen', 'tap-device-creator', 'src/fd-net-device/tap-device-creator', 'raw-sock-creator', 'src/fd-net-device/raw-sock-creator', 'tap-creator', 'src/tap-bridge/tap-creator']
> You must first `sudo ./waf install` from ns-3 which installs ns-3 including ndnSIM system-wide (optimized build is recommended), and then `./waf configure` and `./waf` inside the scenario template.
> 
> Yours, Junxiao
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20170103/c7f42154/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20170103/c7f42154/attachment-0001.bin>