Re: [Boost-bugs] [Boost C++ Libraries] #5752: boost::call_once() is unreliable on some platforms

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #5752: boost::call_once() is unreliable on some platforms
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2012-09-03 14:55:11


#5752: boost::call_once() is unreliable on some platforms
----------------------------------------------------+-----------------------
  Reporter: Matthew Dempsky <matthew@…> | Owner: viboes
      Type: Bugs | Status: assigned
 Milestone: Boost 1.52.0 | Component: thread
   Version: Boost 1.47.0 | Severity: Problem
Resolution: | Keywords: once
----------------------------------------------------+-----------------------

Comment (by fhess):

 Some more info, it seems the problem is due to SIG_ATOMIC_MAX being
 defined in my code when I include once.hpp, but it is not defined in
 once.cpp when the libboost_thread is compiled. By default, cstdint
 doesn't define SIG_ATOMIC_MAX when compiling in c++ mode, unless you
 define {{{__STDC_LIMIT_MACROS}}} before stdint.h is included.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/5752#comment:10>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:10 UTC