RC1 came out on Monday, and it had some problems.

Specifically:

* Some libraries didn't build with ToT clang/libc++ (Locale, Wave and Test)

This is because in C++17, some deprecated library features have been removed. [bind1st, mem_fun, auto_ptr, random_shuffle, etc ]

Boost.Config has support for these removals, but this was ... incomplete.

[ This is on me; I did the partial job of adding these to Config's libc++ support a while back ]

Normally, I would be tempted to say "Well, clang 5 is not shipping yet, and so we can put this off until 1.66.0". But both clang 5 and C++17 are imminent (they will both happen well before the 1.66 release, and so I think we should fix this now. Also, a future version of MSVC will have the same library issues.

So I have committed a fix for Boost.Config that fixes the Boost.Test issues.

Hartmut has fixed most of the Boost.Wave issues.

Artymom has a fix for Boost.Locale.

Windows/MSVC builds look good across the board.

* Boost.Fiber fails to build on Mac OS with anything other than -std=c++03.

There is a fix in develop for this; but there's still a bunch of tests failing.

* There's a problem from the beta in Boost.Math.

The regression regarding boost/math/common_factor_ct.hpp (vs
math_fwd.hpp) seems to be still there. (For details please see the
original mail and replies:
https://lists.boost.org/Archives/boost/2017/07/237452.php)

What I presume is the fix (https://github.com/boostorg/math/pull/75) was
merged into develop about 12 hours ago, some automatic CI tests still
running.

* There's a problem with ScopeExit and Visual C++ 2017

With Visual C++ 2017 and /permissive-, ScopeExit is still broken, for which there's an open PR:
https://github.com/boostorg/scope_exit/pull/3

Looks good otherwise on MSVC 14.11, tested with /std=cpplatest and _HAS_AUTO_PTR_ETC=1, targeting Windows 10 and XP, 32 bit and 64 bit, built as static libraries.