Also working on this issue with MSik hey all,
this looks very much like a linker error because of the reference to symbols, which usually comes up when there is a missing .dylib file and such things.
Static linking is also a type of linking and the output string "[runStaticInitializersOnce]" hints at perhaps a static linking step happening,
"cling JIT session error: Failed to materialize symbols: { (main, { ___clang_call_terminate }) }" looks maybe like JIT (just in time) we are compiling something on the spot and then linking? Hard to parse this bit for clues.
Also, it appears to me from this output:
```
File "/Users/msikka/Downloads/ns-allinone-3.38/ns-3.38/examples/tutorial/first.py", line 35, in <module>
devices = pointToPoint.Install(nodes)
TypeError: none of the 5 overloaded methods succeeded. Full details:
ns3::NetDeviceContainer ns3::PointToPointHelper::Install(std::string aNode, std::string bNode) =>
TypeError: takes at least 2 arguments (1 given)
ns3::NetDeviceContainer ns3::PointToPointHelper::Install(ns3::Ptr<ns3::Node> a, std::string bName) =>
TypeError: takes at least 2 arguments (1 given)
ns3::NetDeviceContainer ns3::PointToPointHelper::Install(std::string aName, ns3::Ptr<ns3::Node> b) =>
TypeError: takes at least 2 arguments (1 given)
ns3::NetDeviceContainer ns3::PointToPointHelper::Install(ns3::NodeContainer c) =>
ValueError: nullptr result where temporary expected
ns3::NetDeviceContainer ns3::PointToPointHelper::Install(ns3::Ptr<ns3::Node> a, ns3::Ptr<ns3::Node> b) =>
TypeError: takes at least 2 arguments (1 given)
```
This looks very much like a Python call, and then the correct C++ function cannot be found. PointToPoint I believed came with core ns-3 and didn't need to be built as a special separate package, and also first.cc compiles and runs just fine, so we at least know that PointToPoint can be found on C++ side,
Also, in this error message, if you notice, it doesn't fail until line 35, which is pretty far down the script, so that makes me believe that perhaps our Python isn't broken per se, but that perhaps we are missing some dylib file that has the PointToPointHelper::Install function we are missing. Perhaps PointToPoint library is dynamically loading at invocation time in Python and then we are exploding because we can't find the symbol we need.
We spent some time googling this issue and didn't find that much, so wanted to query the group and see if anyone else has had such a sighting.