[macOS Sierra] Error when running ./waf

56 views
Skip to first unread message

amudh...@gmail.com

unread,
Mar 17, 2017, 4:25:51 AM3/17/17
to ns-3-users
Hello,

I am trying to get ns-3 up and running on my macbook running macOS Sierra, specifically to use the LAA-WiFi-Coexistence modules. I downloaded a tarball form Mercurial (phase-3 code as linked in https://www.nsnam.org/wiki/LAA-WiFi-Coexistence). When I run ./waf I get the following error: 

In file included from ../src/laa-wifi-coexistence/test/test-lte-unlicensed-interference.cc:47:

../src/laa-wifi-coexistence/test/test-lte-unlicensed-interference.h:60:10: error: private field 'm_expectedUlSinrDb' is not used [-Werror,-Wunused-private-field]

  double m_expectedUlSinrDb;

         ^

1 error generated.


Waf: Leaving directory `/Users/amudheesan/workspace/ns-3-lbt-9529febb7ebc/build'

Build failed

 -> task in 'ns3-laa-wifi-coexistence-test' failed (exit status 1): 

{task 4397303440: cxx test-lte-unlicensed-interference.cc -> test-lte-unlicensed-interference.cc.3.o}

['/usr/bin/clang++', '-O0', '-ggdb', '-g3', '-Wall', '-Werror', '-Wno-unused-local-typedefs', '-Wno-potentially-evaluated-expression', '-I../src/laa-wifi-coexistence', '-fPIC', '-I.', '-I..', '-DNS3_BUILD_PROFILE_DEBUG', '-DNS3_ASSERT_ENABLE', '-DNS3_LOG_ENABLE', '-DHAVE_SYS_IOCTL_H=1', '-DHAVE_IF_NETS_H=1', '-DHAVE_NET_ETHERNET_H=1', '-DNS_TEST_SOURCEDIR="src/laa-wifi-coexistence/test"', '../src/laa-wifi-coexistence/test/test-lte-unlicensed-interference.cc', '-c', '-o', '/Users/amudheesan/workspace/ns-3-lbt-9529febb7ebc/build/src/laa-wifi-coexistence/test/test-lte-unlicensed-interference.cc.3.o']


Any help in this regard will be very useful. Thank you.

-Amu

Steffen Lindner

unread,
Mar 17, 2017, 7:50:48 AM3/17/17
to ns-3-users
Hey, 

thats just a warning that your private variable is not used, but your compiler treats warnings as errors, so you just have to disable this option (or remove the unused variable from the definition).

Kind regards

amudh...@gmail.com

unread,
Mar 17, 2017, 8:13:42 AM3/17/17
to ns-3-users
That fixed the issue, thank you! 
Reply all
Reply to author
Forward
0 new messages