On Wed, Jul 30, 2014 at 5:37 AM, Eric Niebler
On 7/29/2014 12:26 AM, Andrey Semashev wrote:
On Tue, Jul 29, 2014 at 6:55 AM, Andrey Semashev
I can create a pull request to fix this locally in ASIO, if there is a chance to merge it into 1.56. But that will only fix this particular breakage; I can't tell if there are other similar places.
https://github.com/boostorg/asio/pull/7
I tried to compile pion 5.0.6 with gcc 4.4.7 with this change and it succeeded. I'd appreciate if someone could merge it to develop.
This isn't a bug in Asio, so that's the wrong fix (I think). The fix belongs in Boost.Range, and fixing it there will save this kind of heartache for many more people.
I agree. I just though it was too late for massive changes in Boost.Range.
Thomas, Andrey: Can one of you apply the following patch to libs/range and tell me if pion compiles successfully with it. (I've been unsuccessful configuring pion myself.)
https://github.com/boostorg/range/pull/16
Andrey, if you can test this, be sure to revert your change to Asio first.
Clean 1.56 RC + this patch fixes pion 5.0.6 on gcc 4.4.7 for me.