Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1403165

Summary: boost::asio::use_future can't be used on Fedora
Product: [Fedora] Fedora Reporter: Jonathan Wakely <jwakely>
Component: boostAssignee: Jonathan Wakely <jwakely>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: dakingun, denis.arnaud_fedora, fweimer, jwakely, me
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: boost-1.60.0-10.fc25 boost-1.60.0-8.fc24 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-11 19:28:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jonathan Wakely 2016-12-09 10:28:02 UTC
The following code cannot be compiled on any supported version of Fedora:

#include <boost/asio.hpp>
#include <boost/asio/use_future.hpp>

void f(boost::asio::ip::tcp::socket& s, boost::asio::mutable_buffers_1& buf)
{
  std::future<std::size_t> my_future
  = s.async_read_some(buf, boost::asio::use_future);
}

The problem is that the versions of GCC shipped in Fedora do support the use of allocator<void>::construct() that Boost.Asio uses.

This has been fixed in later releases of GCC (by https://gcc.gnu.org/PR78052), but this change to Asio would solve the problem too:

https://github.com/boostorg/asio/commit/42e7869f411a75512fb6994c634eb086fb9eb5cc

Comment 1 Fedora Update System 2016-12-09 15:01:13 UTC
boost-1.60.0-10.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-bdf59f246f

Comment 2 Fedora Update System 2016-12-09 15:01:22 UTC
boost-1.60.0-8.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-0d80628eb6

Comment 3 Fedora Update System 2016-12-09 15:01:27 UTC
boost-1.58.0-12.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-09abe47360

Comment 4 Fedora Update System 2016-12-10 03:53:16 UTC
boost-1.58.0-12.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-09abe47360

Comment 5 Fedora Update System 2016-12-10 03:59:05 UTC
boost-1.60.0-10.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-bdf59f246f

Comment 6 Fedora Update System 2016-12-10 04:29:17 UTC
boost-1.60.0-8.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-0d80628eb6

Comment 7 Fedora Update System 2016-12-11 19:28:12 UTC
boost-1.60.0-10.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2016-12-19 07:52:37 UTC
boost-1.60.0-8.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.