On 08/12/16 11:50 +0000, Jonathan Wakely wrote:
On 06/12/16 01:41 -0000, Joseph Stockman wrote:
Well, it continues to mean the busted version of boost::asio for those who want to utilize any of the C++11 features (futures, etc). We've been forced to drop all Fedora support for our products until that changes.
Are you "Uncle Vlad" on ask.fedoraproject.org?
I explained at
https://ask.fedoraproject.org/en/question/95613/boost-161-on-fedora24/?answer=95700#post-id-95700
that it's impossible to update Boost in a released version of Fedora,
but that we can backport fixes to 1.60 if necessary.
But if people don't bother to report bugs explaining what the problem
is and just whinge about things being busted then I'm not going to do
anything. I don't even know what the problem is, so how am I meant to
fix it?
But answer came there none.
Is it related to this change?
https://github.com/boostorg/asio/commit/42e7869f411a75512fb6994c634eb086fb9eb5cc
I change the definition of std::allocator<void> to make that work
again, so it will be fixed anyway when Fedora gets GCC 6.3 (see
https://gcc.gnu.org/PR78052 for the changes).
I can certainly backport that change to the version of Boost in
Fedora, if someone confirms that I've found the right problem
(although boost::allocate_shared is also affected, so waiting for the
new GCC to land is a better solution).
But again, if nobody reports the problem then nothing gets fixed. This
should not be surprising to anybody.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
