Despite https://clang.llvm.org/cxx_status.html saying:
Clang 3.4 and later implement all of the ISO C++ 2014 standard.
The clang 3.5 suffers from the bug in C++14 mode causing failure of
Boost.Filesystem build with:
error: debug information for auto is not yet supported
error: debug information for auto is not yet supported
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800483
The `compiler` property should trigger creation of `user-config.jam`
with the expected GCC 8 defined.
Something has changed on the GitHub Actions images or Boost.Build
and GCC 8 build job started failing:
/home/runner/work/gil/boost-root/tools/build/src/tools/gcc.jam:203: in gcc.init from module gcc
error: toolset gcc initialization:
error: version '8' requested but 'g++-8' not found and version '7.5.0' of default 'g++' does not match
e.g. https://github.com/boostorg/gil/pull/562/checks?check_run_id=2246393722
The compilers should be `install`-ed explicitly to avoid such issues in future.
Add basic GitHub Actions configuration based on mp11
Remove Actions jobs using GCC 4.7 and 4.8 - unsupported compilers
Run b2 with --abbreviate-paths on Windows
The -std=c++1z is broken for clang-4.0 but no need to test it
Add -mbig-obj to GCC on Windows
- That is to avoid string table overflow and file too big
Define _GLIBCXX_USE_CXX11_ABI=0 for clang 3.5, 3.6, 3.7
- Should help avoid linker error:
`undefined reference to std::ios_base::failure::failure(char const*, std::error_code const&)`
Disable certain check in algorithm_channel_relation test for clang<3.8
