|
Bugzilla – Full Text Bug Listing |
| Summary: | Rephrase "Modules not built" | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | John Abraham <john.abraham.in> |
| Component: | build system | Assignee: | Tom Henderson <tomh> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ns-bugs, tomh |
| Priority: | P5 | ||
| Version: | pre-release | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | patch to fix | ||
|
Description
John Abraham
2012-10-11 01:06:00 UTC
(In reply to comment #0) > Currently we display > Modules built: > antenna aodv applications > bridge buildings config-store > core csma csma-layout > dsdv dsr energy > flow-monitor internet lte > mesh mobility mpi > netanim (no Python) network nix-vector-routing > olsr point-to-point point-to-point-layout > propagation spectrum stats > test (no Python) tools topology-read > uan virtual-net-device wifi > wimax > > Modules not built: > click emu openflow > tap-bridge visualizer > > Several users since perhaps ns-3.11 have panicked when they see "Modules not > built", needing email exchanges to explain this. > > It will help greatly if we re-phrase "Modules not built" or print an additional > line pointing the user to some README explaining this. > In the README we could mention , that some modules are built only on explicit > request and their absence will not impact normal functioning of the simulator How about putting this into the tutorial here, instead of the README? http://www.nsnam.org/docs/tutorial/html/getting-started.html#building-ns-3 Sure , a pointer to the tutorial is also good. Hopefully we can dedicate a small section related to explaining "Modules not built" in the tutorial. Like: Modules not built: (Refer http://www.nsnam.org/.....) emu openflow This can potentially reduce the number of users who consider "Modules not built" as an ERROR and avoid needing to send email to ns-3-users. (In reply to comment #0) > Currently we display > Modules built: > antenna aodv applications > bridge buildings config-store > core csma csma-layout > dsdv dsr energy > flow-monitor internet lte > mesh mobility mpi > netanim (no Python) network nix-vector-routing > olsr point-to-point point-to-point-layout > propagation spectrum stats > test (no Python) tools topology-read > uan virtual-net-device wifi > wimax > > Modules not built: > click emu openflow > tap-bridge visualizer > > Several users since perhaps ns-3.11 have panicked when they see "Modules not > built", needing email exchanges to explain this. > > It will help greatly if we re-phrase "Modules not built" or print an additional > line pointing the user to some README explaining this. > In the README we could mention , that some modules are built only on explicit > request and their absence will not impact normal functioning of the simulator (In reply to comment #1) > (In reply to comment #0) > > Currently we display > > Modules built: > > antenna aodv applications > > bridge buildings config-store > > core csma csma-layout > > dsdv dsr energy > > flow-monitor internet lte > > mesh mobility mpi > > netanim (no Python) network nix-vector-routing > > olsr point-to-point point-to-point-layout > > propagation spectrum stats > > test (no Python) tools topology-read > > uan virtual-net-device wifi > > wimax > > > > Modules not built: > > click emu openflow > > tap-bridge visualizer > > > > Several users since perhaps ns-3.11 have panicked when they see "Modules not > > built", needing email exchanges to explain this. > > > > It will help greatly if we re-phrase "Modules not built" or print an additional > > line pointing the user to some README explaining this. > > In the README we could mention , that some modules are built only on explicit > > request and their absence will not impact normal functioning of the simulator > > How about putting this into the tutorial here, instead of the README? > http://www.nsnam.org/docs/tutorial/html/getting-started.html#building-ns-3 Created attachment 1479 [details]
patch to fix
planning to apply for ns-3.16 if no further comments
pushed in changeset: f8bff624db3c |