[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#653823: More info on Known Fixes



Some more info on items in the "Known Fixes" category follows.

Parse error at "BOOST_JOIN"
---------------------------
Tag [moc]

The parse error is from Qt's tools moc and lconvert.  These tools do
not handle the entire C++ language; see the Qt issue
https://bugreports.qt.nokia.com/browse/QTBUG-22829

The workaround is to abuse the Boost header guards by defining it
on the moc/lconvert command line, thus avoiding having to parse
the boost headers.  Pass -DBOOST_TT_HAS_OPERATOR_HPP_INCLUDED
to the moc invocation.  If using cmake:

  QT4_WRAP_CPP(sources ${moc-sources} OPTIONS -DBOOST_TT_HAS_OPERATOR_HPP_INCLUDED)


'boost::asio::ip::tcp::acceptor' has no member named 'io_service'
-----------------------------------------------------------------
Tag [io_service]

Boost 1.47 removed a deprecated function [1]:

  Removed the deprecated member functions named io_service(). The get_io_service() member functions should be used instead. 

The get_io_service() function is available in the current default
Boost (version 1.46.1) [2], so the change can be made now.

[1] http://www.boost.org/doc/libs/1_48_0/doc/html/boost_asio/history.html
[2] http://www.boost.org/doc/libs/1_46_1/doc/html/boost_asio/reference/ip__tcp/acceptor.html


Removal of boost::details::pool::singleton_default
--------------------------------------------------
Tag [singleton]

Prior to 1.48, Boost.Pool used a singleton base class.  It was an
implementation detail, now removed, but some external packages
depended upon it.  This is an upstream bug, since the class was never
intended as a public interface.

The breakage may manifest in a couple of ways:

* boost/pool/detail/singleton.hpp: No such file or directory
* 'singleton_default' in namespace 'boost::details::pool' does not name a type

The class in singleton.hpp is small enough that it could simply be
included directly into the using source code.


Attachment: signature.asc
Description: Digital signature


Reply to: