On Sat, Oct 27, 2018 at 8:15 PM John Maddock via Boost wrote:

igaztanaga-develop-gcc-3.4c++03 cc1plus.exe: error: unrecognized command line option "-fvisibility-inlines-hidden" cc1plus.exe: error: unrecognized command line option "-fvisibility=hidden"

These are likely caused by the recent addition of the visibility flags to the compiler and linker, and gcc 3.4 doesn't support visibility. I don't think it is worthwhile trying to support that old compiler.

On Sat, Oct 27, 2018 at 12:14 PM John Maddock via Boost < boost@lists.boost.org> wrote:

There are rather a lot of test runners that fail all tests due to setup errors:

teeks99-02-dc3.1-11-Docker-64on64 /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/functional:2194:2:

error: no type named 'type' in 'std::enable_if' (and more errors from <functional> - the compiler appears to be unable to handle the std lib headers so I'm not sure what the point of testing it is?)

This strikes me as odd. The teeks99-02-dc3.0-11-Docker-64on64 is an *older* version of clang, on the same version of ubuntu, but doesn't have this issue. Is it possible this is an issue with boost's detecting of compiler/stdlib capabilities that isn't working correctly here? If anyone wants to play with this, the images on docker hub teeks99/boost-cpp-docker:clang-3.0 and clang-3.1 (and clang-3.2 which is again happy) can be used to figure out what is happening. All three use the same ubuntu install (trusty), have identical Dockerfiles (except the clang version), and use nearly identical lines in their user-config.jam files. using clang : 3.1~c++11 : clang++-3.1 : <cxxflags>"-Wno-c99-extensions -std=c++11" ; Tom