Bug 1625 - ns-3-dev fails to build on Debian wheezy amd64
ns-3-dev fails to build on Debian wheezy amd64
Status: RESOLVED FIXED
Product: ns-3
Classification: Unclassified
Component: lte
pre-release
All All
: P5 normal
Assigned To: Nicola Baldo
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-13 09:27 UTC by Vedran Miletić
Modified: 2013-04-15 12:36 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vedran Miletić 2013-04-13 09:27:06 UTC
With the latest LENA changes included in ns-3-dev on Debian wheezy amd64 I'm getting:

src/lte/bindings/ns3module.cc: In function ‘void PyNs3LteGlobalPathlossDatabase__tp_clear(PyNs3LteGlobalPathlossDatabase*)’:
src/lte/bindings/ns3module.cc:37979:16: error: deleting object of abstract class type ‘ns3::LteGlobalPathlossDatabase’ which has non-virtual destructor will cause undefined behaviour [-Werror=delete-non-virtual-dtor]
src/lte/bindings/ns3module.cc: In function ‘void PyNs3UplinkLteGlobalPathlossDatabase__tp_clear(PyNs3UplinkLteGlobalPathlossDatabase*)’:
src/lte/bindings/ns3module.cc:72126:16: error: deleting object of polymorphic class type ‘ns3::UplinkLteGlobalPathlossDatabase’ which has non-virtual destructor might cause undefined behaviour [-Werror=delete-non-virtual-dtor]
src/lte/bindings/ns3module.cc: In function ‘void PyNs3DownlinkLteGlobalPathlossDatabase__tp_clear(PyNs3DownlinkLteGlobalPathlossDatabase*)’:
src/lte/bindings/ns3module.cc:75377:16: error: deleting object of polymorphic class type ‘ns3::DownlinkLteGlobalPathlossDatabase’ which has non-virtual destructor might cause undefined behaviour [-Werror=delete-non-virtual-dtor]
cc1plus: all warnings being treated as errors
Comment 1 Vedran Miletić 2013-04-13 10:40:30 UTC
I'm getting the same issue on Ubuntu 13.04 prerelease amd64.
Comment 2 Tom Henderson 2013-04-13 16:00:23 UTC
I plan to add a virtual destructor to the base class, fix the bindings, and check in later today if all goes well.
Comment 3 Tom Henderson 2013-04-15 01:02:31 UTC
fixed in: eb7335c2423c
Comment 4 Vedran Miletić 2013-04-15 12:36:42 UTC
Thanks, works now.