Re: [Boost-users] [serialization] Known way to handle this?

Subject: Re: [Boost-users] [serialization] Known way to handle this?
From: Jeffrey Lee Hellrung, Jr. (jeffrey.hellrung_at_[hidden])
Date: 2012-11-05 22:52:18

On Mon, Nov 5, 2012 at 2:36 PM, Lemay.Steve <Steve.Lemay_at_[hidden]> wrote:

> Is there already a known [proper] way to correct his issue (shown below)?
>  I had reported it during the beta – this occurs many times for various
> source.****
>
> ** **
>
>     "QCC" -Wc,-ftemplate-depth-128 -DFD_SETSIZE=2048 -march=k8-sse3
> -mtune=k8-sse3 -mmmx -msse3 -mfpmath=sse -mno-3dnow -mstackrealign -Y_cpp
> -Wc,-fPIC,-fnothrow-opt,-std=c++11,-std=gnu++11 -O3 -Wc,-finline-functions
> -Wc,-Wno-inline -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o
> "D:\boostBuild_QCC_1_52_0\boost\bin.v2\libs\serialization\build\qcc\release\link-static\target-os-qnxnto\threadapi-pthread\threading-multi\xml_iarchive.o"
> "libs\serialization\src\xml_iarchive.cpp"****
>
> ** **
>
> ...failed qcc.compile.c++
> D:\boostBuild_QCC_1_52_0\boost\bin.v2\libs\serialization\build\qcc\release\link-static\target-os-qnxnto\threadapi-pthread\threading-multi\xml_iarchive.o...
> ****
>
> qcc.compile.c++
> D:\boostBuild_QCC_1_52_0\boost\bin.v2\libs\serialization\build\qcc\release\link-static\target-os-qnxnto\threadapi-pthread\threading-multi\xml_archive_exception.o
> ****
>
> In file included from
> libs\serialization\src\xml_archive_exception.cpp:21:0:****
>
> ./boost/archive/xml_archive_exception.hpp:35:44: error: looser throw
> specifier for 'virtual
> boost::archive::xml_archive_exception::~xml_archive_exception()'****
>
> In file included from ./boost/archive/xml_archive_exception.hpp:25:0,****
>
>                  from libs\serialization\src\xml_archive_exception.cpp:21:
> ****
>
> ./boost/archive/archive_exception.hpp:86:5: error:   overriding 'virtual
> boost::archive::archive_exception::~archive_exception() throw ()'****
>
> cc:
> d:/qnxsdk/qnxsdk6.5-001/host/win32/x86/usr/lib/gcc/i486-pc-nto-qnx6.5.0/4.7.2/cc1plus
> caught signal 1
>

This looks like an issue in Boost.Serialization. Your best bet is to file a
trac ticket, attach a patch, and prod the list and/or author.

I added "[serialization]" to the subject to increase the chances this'll be
seen by Robert.

Your mentioned this occurs many times for various source(s?). Is it
isolated to the Boost.Serialization sources, or do you get this warning
elsewhere as well?

- Jeff