Hello Tom, On Tue, Nov 21, 2017 at 7:16 PM, Tom Kent <lists@teeks99.com> wrote:

On Mon, Nov 20, 2017 at 9:06 PM, Tom Kent <lists@teeks99.com> wrote:

...

I was able to get to the bottom of this, I hope the libc++ builds start cycling normally now.

...

This was marked (by me!) as a clang bug - that was fixed in clang trunk in January 2013. I find it hard to believe that you're running a clang built from those sources.

-- Marshall

It turns out I had put in a script patch the broken ubuntu header:

https://github.com/teeks99/boost-cpp-docker/blob/11e6d31ca8d28dee8bbb5536f28...

This was a very brittle patch, and when ubuntu fixed it upstream (just two months ago!) it caused some kind of conflict. I've removed the patch from my teeks99/boost-cpp-docker images, so the clang-3.9, -4, -5, and -6 images should be able to use libc++ correctly now.

Thanks for all who helped me straighten this out!

There was a further issue with the need for a `-lc++abi` linker option, it has been added and the results look better now.

Yes, Boost.Contract regression tests now pass on this compiler/platform. The issue was fixed. Thanks a lot. --Lorenzo