Bug 969183 - RHEL 6 boost not compatible with DTS gcc
RHEL 6 boost not compatible with DTS gcc
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: boost (Show other bugs)
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Petr Machata
Miroslav Franc
Depends On:
Blocks: 1056252
  Show dependency treegraph
Reported: 2013-05-30 16:28 EDT by Petr Machata
Modified: 2016-01-31 21:28 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-10-14 02:22:21 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Fix for this issue (631 bytes, patch)
2013-05-30 16:28 EDT, Petr Machata
no flags Details | Diff

  None (edit)
Description Petr Machata 2013-05-30 16:28:10 EDT
Created attachment 755041 [details]
Fix for this issue

Description of problem:
Boost as shipped with RHEL 6 fails to detect threading support in recent GCC's (such as those shipped with DTS).  See this for more details:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Attempt to build boost with recent (post-4.7) GCC.
2. Compile the following program against recent Boost headers:

Actual results:
#include <boost/thread.hpp>
In file included from ./boost/thread/detail/platform.hpp:17:0,
                 from ./boost/thread/thread.hpp:12,
                 from ./boost/thread.hpp:13,
                 from ../x.cc:1:
./boost/config/requires_threads.hpp:29:4: ошибка: #error "Threading support unavaliable: it has been explicitly disabled with BOOST_DISABLE_THREADS"

Expected results:
Comment 3 errata-xmlrpc 2014-10-14 02:22:21 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.