Boost C++ Libraries: Ticket #7335: Using Boost.Pool requires to link with Boost.System

cc set

Wed, 10 Oct 2012 09:08:59 GMT

cc flast@… added

This bug caused by r76543.

New dependencies tree:

pool/detail/mutex.hpp
-> thread/mutex.hpp
   -> thread/(pthread|win32)/mutex.hpp
      -> thread/exceptions.hpp
         -> system/error_code.hpp

Wed, 10 Oct 2012 09:24:36 GMT

As far as I know, Boost.Thread never promised to be header-only or have header-only parts. Thus, using mutex from Boost.Thread and claiming to be header-only seems to me... erm... a bit unfair, even if it used to work somehow.

I think the best solution would be to switch to using <boost/detail/lightweight_mutex.hpp>, as it is header only and does not have any extra dependencies.

cc changed

vslavik@… — Mon, 25 Feb 2013 17:43:20 GMT

cc vslavik@… added

cc changed

bimargulies@… — Sat, 08 Jun 2013 14:40:23 GMT

cc bimargulies@… added

Is there any way around this to disable the use of the mutex?

manuel.freiberger@… — Wed, 07 Aug 2013 18:09:03 GMT

Replying to bimargulies@…:

Is there any way around this to disable the use of the mutex?

I also stumbled across this bug. The pool library pulls the header <boost/thread/mutex.hpp> even if the user has defined BOOST_NO_MT or BOOST_POOL_NO_MT.

It would be good to change line 13 of <boost/thread/mutex.hpp> from #ifdef BOOST_HAS_THREADS to #if defined(BOOST_HAS_THREADS) && !defined(BOOST_NO_MT) && !defined(BOOST_POOL_NO_MT) (this is the complement of the expression from line 32).

This would allow to use Boost.Pool without depending on Boost.System.

status changed; resolution set

Marshall Clow — Tue, 18 Mar 2014 15:21:28 GMT

status new → closed
resolution → duplicate

This is a duplicate of #7085