Opened 14 years ago
Closed 14 years ago
#2193 closed Patches (fixed)
exception: boost::exception_detail::bad_alloc_impl does not provide an explicit destructor for gcc/qcc
Reported by: | Owned by: | Emil Dotchevski | |
---|---|---|---|
Milestone: | Boost 1.37.0 | Component: | exception |
Version: | Boost Development Trunk | Severity: | Problem |
Keywords: | Cc: |
Description
Building the latest version the following error arises:
qcc.compile.c++ ../../bin.v2/libs/test/build/qcc-4.2.3/release/execution_monitor.o In file included from ../../boost/throw_exception.hpp:40, from ../../boost/shared_ptr.hpp:31, from ../../boost/test/utils/callback.hpp:21, from ../../boost/test/execution_monitor.hpp:38, from ../../boost/test/impl/execution_monitor.ipp:30, from ../../libs/test/src/execution_monitor.cpp:16: ../../boost/exception/enable_current_exception.hpp:34: error: looser throw specifier for 'virtual boost::exception_detail::bad_alloc_impl::~bad_alloc_impl()' ../../boost/exception/enable_current_exception.hpp:24: error: overriding 'virtual boost::exception_detail::clone_base::~clone_base() throw ()' cc: /usr/qnx632/host/qnx6/x86/usr/lib/gcc/i386-pc-nto-qnx6.3.0/4.2.3/cc1plus error 1 "QCC" -Wc,-ftemplate-depth-100 -O3 -Wc,-finline-functions -Wc,-Wno-inline -shared -I/usr/pkg/include -DBOOST_ALL_NO_LIB=1 -DBOOST_TEST_DYN_LINK=1 -DNDEBUG -I"../.." -c -o "../../bin.v2/libs/test/build/qcc-4.2.3/release/execution_monitor.o" "../../libs/test/src/execution_monitor.cpp" ...failed qcc.compile.c++ ../../bin.v2/libs/test/build/qcc-4.2.3/release/execution_monitor.o...
It is fixed by the attached patch for me.
Attachments (1)
Change History (4)
by , 14 years ago
Attachment: | fix_looser_throw_specifier_in_bad_alloc_impl.diff added |
---|
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Component: | None → exception |
---|---|
Owner: | set to |
comment:3 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
This ticket belongs to the component 'exception'. Could somebody please change this? The component 'exception' was added after the creation of this ticket (as stated in the ticket #2197).