Bugzilla – Bug 310
Python Bindings Build Error in Cygwin
Last modified: 2008-09-04 08:45:01 UTC
have pygccxml,gccxml [470/530] cxx: build/debug/bindings/python/ns3module.cc -> build/debug/bindings/ python/ns3module_3.o In file included from debug/bindings/python/ns3module.cc:1: debug/bindings/python/ns3module.h: In member function `void PyNs3PacketCounterCa lculator__PythonHelper::Output__parent_caller(ns3::DataOutputCallback&)': debug/bindings/python/ns3module.h:6136: error: cannot call member function `void ns3::CounterCalculator<T>::Output(ns3::DataOutputCallback&) const [with T = uns igned int]' without object debug/bindings/python/ns3module.h: In member function `void PyNs3PacketSizeMinMa xAvgTotalCalculator__PythonHelper::Output__parent_caller(ns3::DataOutputCallback &)': debug/bindings/python/ns3module.h:6213: error: cannot call member function `void ns3::MinMaxAvgTotalCalculator<T>::Output(ns3::DataOutputCallback&) const [with T = unsigned int]' without object debug/ns3/basic-data-calculators.h: In member function `void ns3::CounterCalcula tor<T>::Output(ns3::DataOutputCallback&) const [with T = unsigned int]': debug/bindings/python/ns3module.h:5781: instantiated from here debug/ns3/basic-data-calculators.h:181: error: call of overloaded `OutputSinglet on(const std::string&, const char[6], const unsigned int&)' is ambiguous debug/ns3/data-output-interface.h:52: note: candidates are: virtual void ns3::Da taOutputCallback::OutputSingleton(std::string, std::string, int) debug/ns3/data-output-interface.h:56: note: virtual void ns3::DataOutputCallbac k::OutputSingleton(std::string, std::string, uint32_t) debug/ns3/data-output-interface.h:60: note: virtual void ns3::DataOutputCallbac k::OutputSingleton(std::string, std::string, double) debug/ns3/data-output-interface.h:64: note: virtual void ns3::DataOutputCallbac k::OutputSingleton(std::string, std::string, std::string) <near match> debug/bindings/python/ns3module.h:5996: instantiated from here debug/ns3/basic-data-calculators.h:97: error: call of overloaded `OutputSingleto n(const std::string&, const char[4], const unsigned int&)' is ambiguous debug/ns3/data-output-interface.h:52: note: candidates are: virtual void ns3::Da taOutputCallback::OutputSingleton(std::string, std::string, int) debug/ns3/data-output-interface.h:56: note: virtual void ns3::DataOutputCallbac k::OutputSingleton(std::string, std::string, uint32_t) debug/ns3/data-output-interface.h:60: note: virtual void ns3::DataOutputCallbac k::OutputSingleton(std::string, std::string, double) debug/ns3/data-output-interface.h:64: note: virtual void ns3::DataOutputCallbac k::OutputSingleton(std::string, std::string, std::string) <near match> debug/ns3/basic-data-calculators.h:98: error: call of overloaded `OutputSingleto n(const std::string&, const char[4], const unsigned int&)' is ambiguous debug/ns3/data-output-interface.h:52: note: candidates are: virtual void ns3::Da taOutputCallback::OutputSingleton(std::string, std::string, int) debug/ns3/data-output-interface.h:56: note: virtual void ns3::DataOutputCallbac k::OutputSingleton(std::string, std::string, uint32_t) debug/ns3/data-output-interface.h:60: note: virtual void ns3::DataOutputCallbac k::OutputSingleton(std::string, std::string, double) debug/ns3/data-output-interface.h:64: note: virtual void ns3::DataOutputCallbac k::OutputSingleton(std::string, std::string, std::string) <near match> Build failed
This is due to a gccxml bug: http://www.gccxml.org/Bug/view.php?id=7572 You might get away with it by re-scanning API definitions from within the cygwin environment (./waf --python-scan). However the most likely solution will probably have to be that we disable python bindings in CygWin. If you really care about Python bindings, try building with mingw and native python instead.
*** This bug has been marked as a duplicate of bug 297 ***
(In reply to comment #1) > This is due to a gccxml bug: http://www.gccxml.org/Bug/view.php?id=7572 > > You might get away with it by re-scanning API definitions from within the > cygwin environment (./waf --python-scan). However the most likely solution > will probably have to be that we disable python bindings in CygWin. > > If you really care about Python bindings, try building with mingw and native > python instead. > I added the above information to the python wiki page and linked to it from the Troubleshooting page.