Difference between revisions of "Ns-3.29-errata"

From Nsnam
Jump to: navigation, search
(start ns-3.29 errata page)
(No difference)

Revision as of 19:16, 20 September 2018

Main Page - Current Development - Developer FAQ - Tools - Related Projects - Project Ideas - Summer Projects

Installation - Troubleshooting - User FAQ - HOWTOs - Samples - Models - Education - Contributed Code - Papers

Errata against ns-3.29 release

The following issues have been identified since the ns-3.29 release, and will be addressed in a future ns-3.29.1 release update.

MacOs Clang 10 compatibility: Shortly after the ns-3.29 release, a MacOs Clang compiler update was issued; this causes the ns-3 build to fail as follows:

   ./ns3/make-event.h:665:20: error: unused typedef 'F' [-Werror,-Wunused-local-typedef]
   typedef void (*F)(U1, U2, U3);
                  ^
   ./ns3/make-event.h:699:20: error: unused typedef 'F' [-Werror,-Wunused-local-typedef]
   typedef void (*F)(U1, U2, U3, U4);
                  ^
   ./ns3/make-event.h:633:20: error: unused typedef 'F' [-Werror,-Wunused-local-typedef]
   typedef void (*F)(U1, U2);
                  ^
   ./ns3/make-event.h:665:20: error: unused typedef 'F' [-Werror,-Wunused-local-typedef]
   typedef void (*F)(U1, U2, U3);
                  ^
   4 errors generated.

This can be worked around by passing the '--disable-werror' flag to Waf configuration step; e.g.:

   ./waf configure --disable-werror --enable-examples --enable-tests

API scan for ns-allinone-3.29: The version of pybindgen associated with ns-allinone-3.29 is incorrect, and the bindings toolchain will not install correctly. An example error output is:

       from pybindgen.castxmlparser import ModuleParser, PygenClassifier, PygenSection, WrapperWarning, find_declaration_from_name
       ImportError: No module named castxmlparser

One workaround is replace the 'bakeconf.xml' with the version corresponding to this changeset:

Python 3.7 and API scanning toolchain: ArchLinux has started to distribute Python 3.7, but there are issues with compatibility of the toolchain.

There is no present workaround other than piecing together the hints found in the above bug report.