[ndnSIM] problem with an underwater node while running, the NDN layer!

Narges Mehran narges.mehran at gmail.com
Mon Sep 11 09:22:18 PDT 2017


Thanks a lot Junxiano and Spyros. Yes, both of you were right. The old
version of ndnSIM is also running on my system. By removing the redundant
libraries, 'build' finished successfully.

About the "socket-based application" Spyros mentioned, I've understood that
in order to work with UAN library, running a socket program is necessary.
If I run a socket with a specific application, I will have to modify the
Producer/Consumer application to support both the "Named Data" and "Socket"
concepts. Therefore, I thought that an application like Chronosync can help
me more. If there is other applications (like websocketpp), I am looking
forward to hearing from you.

On Mon, Sep 11, 2017 at 4:34 AM, Spyridon (Spyros) Mastorakis <
mastorakis at cs.ucla.edu> wrote:

> Hi,
> as Junxiao has mentioned already, most probably there are multiple
> versions of NS-3 installed somewhere on your system, therefore, chronoSync
> is not linked against the appropriate version of NS-3.
> Moreover, it is not clear to me what you meant by “socket-based
> application”. To my understanding, the Socket class of ChronoSync is merely
> a programming abstraction for data publishing, rather than a “real” network
> socket of today’s client-server communication paradigm.
> Hope that this helps,
> Spyridon (Spyros) Mastorakis
> Personal Website: http://cs.ucla.edu/~mastorakis/
> Internet Research Laboratory
> Computer Science Department
> On Sep 10, 2017, at 4:33 PM, Junxiao Shi <shijunxiao at email.arizona.edu>
> wrote:
> Hi Narges
> This indicates an error in linker command line. You may inspect './waf
> configure' output, build/config.log file, and the ld invocation printed
> after the quoted error message to learn about the error.
> The solution typically involves removing duplicate library versions
> installed into the system, and adjusting wscript.
> If you need more help, provide complete information as requested on
> http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2016-May/001748.html
> Yours, Junxiao
> On Mon, Sep 11, 2017 at 03:52 Narges Mehran <narges.mehran at gmail.com>
> wrote:
>> Hello ndnSIM team,
>> It seems that I should run a socket-based application, such as the
>> "ChronoSync", on UAN nodes.
>> I am following this link: https://github.com/spirosmastorakis/scenario-
>> ChronoSync
>> While running the "./waf", this error comes up!
>> Vostro1310:~/ndnSIM2.1/scenario-ChronoSync$ ./waf
>> Waf: Entering directory `/home/narguess/ndnSIM2.1/
>> scenario-ChronoSync/build'
>> [13/13] Linking build/chronosync-simple
>> /usr/local/lib/libns3-dev-emu-optimized.so: undefined reference to
>> `ns3::LogComponent::LogComponent(std::string const&, ns3::LogLevel)'
>> collect2: error: ld returned 1 exit status
>> Regards,
>> Narges
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20170911/f15e1d36/attachment.html>

More information about the ndnSIM mailing list