March 2018 - Boost - lists.boost.org

[boost.test] merging minor changes to master
by Raffi Enficiaud 01 Apr '18

01 Apr '18

Hi list, I merged a very minor commit that will make MinGW people happy. Rev of Boost.test on master is now 413b2f660118060db732dbf38a2bdffb527395e3 . Since Beta1: * doc updates * small bugfix PR 134 * include all lower case on windows for MinGW. PR 136 I would be grateful to the release managers if those changes go to the final 1.67 release. Thanks, Raffi

1 0

Maintenance of boostorg on AppVeyor
by Mateusz Loskot 30 Mar '18

30 Mar '18

Hi, I found [1] there is boostorg account on AppVeyor https://ci.appveyor.com/project/boostorg/boost/ There seem to be no sites/URLs per GitHub repo, eg. https://ci.appveyor.com/project/boostorg/hana https://ci.appveyor.com/project/boostorg/gil etc. I'm unclear how this is setup, but boostorg/boost seems to be a sink for all boostorg repos on GitHub. What is the purpose of this AppVeyor boostorg account? Can library maintainers have access to this account and use to build their library repo? If yes, where can I request to set-up AppVeyor roles [2] for Boost.GIL maintainers, so they can cancel/re-run builds? Or, is it that typically maintainers are supposed to create sparate account for builds a library, eg. ci.appveyor.com/project/mloskot/gil Isn't such duplication of builds a waste of resources? [1] https://lists.boost.org/Archives/boost/2015/06/223325.php [2] https://www.appveyor.com/docs/team-setup/#github-integration Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

Failing to use b2/bjam including libraries with Clang
by Paul A. Bristow 30 Mar '18

30 Mar '18

I am still failing to get Clang on Windows 10 to work with b2/bjam *linking to libraries*. I have a few simple test cases, using Boost.System to display an error code ,using Boost.Test for a 'hello World" use of Boost.Test, and a simple regex example1 linking to Boost.Regex library. All links to libraries are static (to avoid reported problems with DLL and Clang). I have tried to use the LLD linker http://releases.llvm.org/6.0.0/tools/lld/docs/ReleaseNotes.html as some have recommended this, but not successfully with libraries, so far. Things that DO work OK with Clang 6.0.0 are 1 Visual Studio IDE (using Boost prebuilt libraries) Platform Toolset = llvm-2014 and MS linker only. 2 Codeblocks IDE (mingw64 on windows 10) (using normal Boost prebuilt libraries as part of the normal install) and clang++.exe. (But NOT when using the LTO lld.exe linker getting error: Expected a single module ???- but I am not trying to use C++ modules!). 3 Using b2/bjam to run a *single* exe (no libraries). jamfile is just [ run hello_boost.cpp ] with >b2 toolset=gcc-7.2.0,msvc-14.1,clang-6.0.0 4 Using all examples in jamfile b2/bjam with libraries with toolset=gcc-7.2.0,msvc-14.1 (so I am confident that it is not a problem with the C++ or the jamfile). What *doesn't work* is b2/bjam using a library with toolset=clang-6.0.0, neither using clang++ linker nor using LTO llvm-lld.exe. And since I want to write b2 -a -j6 --debug-configuration -d2 toolset=msvc-14.1,gcc-7.2.0,clang-6.0.0 address-model=64 > my.log this is most disappointing :-( My user-config.jam contains using clang : # Version. 6.0.0 : # Location of Clang compiler .exe file(s). "C:/LLVM/clang-600/LLVM/bin/clang++.exe" : # Options. <compileflags>-v <compileflags>-m64 <compileflags>-fmsc-version=1900 <compileflags>--target=i686-pc-windows-msvc <define>_CRT_SECURE_NO_DEPRECATE <define>_CRT_SECURE_NO_WARNINGS <cxxflags>-std=c++17 <cxxflags>-flto=thin <<<<<<< if trying to use LTO lld linker <cxxflags>-Wno-deprecated <cxxflags>-Wno-deprecated-declarations <linkflags>-v <linkflags>-fuse-ld=lld <<<<<<< if trying to use LTO lld linker <linkflags>-flto=thin <<<<<<< if trying to use LTO lld linker <linkflags>--verbose <linkflags>-m64 <linkflags>--target=i686-pc-windows-msvc <linkflags>-lmsvcrt The Boost.Test and Boost.System libraries are built as expected (for Clang) at "..\..\..\bin.v2\libs\system\build\clang-gnu-linux-6.0.0\release\address-model-64\link-static\threadapi-win32\libboost_system-clang6 0-x64-1_66.lib" my jamfile contains lines like [ run hello_boost_system.cpp ../../system/build//boost_system/<link>static ] [ run hello_boost_test.cpp : : : <library>/boost/test//boost_unit_test_framework/<link>static ] After trying a bewildering array of linkers, and many options, I finally always end up with a series of link failures with errors either like error: lto.tmp: undefined symbol: ? system_category@system@boost@@YAAEBVerror_category@12@XZ or a missing entry point: LINK : fatal error LNK1561: entry point must be defined (This appears to be a message from MSVC, not the lld linker?) clang-linux.link ..\..\..\bin.v2\libs\hello_boost_test\test\hello_boost_system.test\clang-gnu-linux-6.0.0\release\address-model-64\threadapi-win32\he llo_boost_system.exe "C:/LLVM/clang-600/LLVM/bin/clang++.exe" -o "..\..\..\bin.v2\libs\hello_boost_test\test\hello_boost_system.test\clang-gnu-linux-6.0.0\release\address-model-64\threadapi-win32\h ello_boost_system.exe" -Wl,--start-group "..\..\..\bin.v2\libs\hello_boost_test\test\hello_boost_system.test\clang-gnu-linux-6.0.0\release\address-model-64\threadapi-win32\h ello_boost_system.obj" "..\..\..\bin.v2\libs\system\build\clang-gnu-linux-6.0.0\release\address-model-64\link-static\threadapi-win32\libboost_system-clang6 0-x64-1_66.lib" -Wl,-Bstatic -Wl,-Bdynamic -Wl,--end-group -v -fuse-ld=lld -flto=thin --verbose -m64 --target=i686-pc-windows-msvc -lmsvcrt -m64 clang version 6.0.0 (tags/RELEASE_600/final) Target: x86_64-pc-windows-msvc Thread model: posix InstalledDir: C:\LLVM\clang-600\LLVM\bin "C:\\LLVM\\clang-600\\LLVM\\bin\\lld-link" "-out:..\\..\\..\\bin.v2\\libs\\hello_boost_test\\test\\hello_boost_system.test\\clang-gnu-linux-6.0.0\\release\\address-model-64\\t hreadapi-win32\\hello_boost_system.exe" -defaultlib:libcmt "-libpath:C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Professional\\VC\\Tools\\MSVC\\14.13.26128\\lib\\x64" "-libpath:C:\\Program Files (x86)\\Windows Kits\\10\\Lib\\10.0.16299.0\\ucrt\\x64" "-libpath:C:\\Program Files (x86)\\Windows Kits\\10\\Lib\\10.0.16299.0\\um\\x64" -nologo --start-group "..\\..\\..\\bin.v2\\libs\\hello_boost_test\\test\\hello_boost_system.test\\clang-gnu-linux-6.0.0\\release\\address-model-64\\thread api-win32\\hello_boost_system.obj" "..\\..\\..\\bin.v2\\libs\\system\\build\\clang-gnu-linux-6.0.0\\release\\address-model-64\\link-static\\threadapi-win32\\libboost_s ystem-clang60-x64-1_66.lib" -Bstatic -Bdynamic --end-group msvcrt.lib C:\LLVM\clang-600\LLVM\bin\lld-link: warning: ignoring unknown argument: --start-group C:\LLVM\clang-600\LLVM\bin\lld-link: warning: ignoring unknown argument: -Bstatic C:\LLVM\clang-600\LLVM\bin\lld-link: warning: ignoring unknown argument: -Bdynamic C:\LLVM\clang-600\LLVM\bin\lld-link: warning: ignoring unknown argument: --end-group C:\LLVM\clang-600\LLVM\bin\lld-link: error: lto.tmp: undefined symbol: ?system_category@system@boost@@YAAEBVerror_category@12@XZ C:\LLVM\clang-600\LLVM\bin\lld-link: error: lto.tmp: undefined symbol: ?generic_category@system@boost@@YAAEBVerror_category@12@XZ clang++.exe: error: linker command failed with exit code 1 (use -v to see invocation) Which seems to indicate some link problem finding error_category (error_category is found OK with GCC or MSVC)? and for a simple use of Boost.Test library clang version 6.0.0 (tags/RELEASE_600/final) Target: x86_64-pc-windows-msvc Thread model: posix InstalledDir: C:\LLVM\clang-600\LLVM\bin "C:\\LLVM\\clang-600\\LLVM\\bin\\lld-link" "-out:..\\..\\..\\bin.v2\\libs\\hello_boost_test\\test\\hello_boost_test.test\\clang-gnu-linux-6.0.0\\release\\address-model-64\\thr eadapi-win32\\hello_boost_test.exe" -defaultlib:libcmt "-libpath:C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Professional\\VC\\Tools\\MSVC\\14.13.26128\\lib\\x64" "-libpath:C:\\Program Files (x86)\\Windows Kits\\10\\Lib\\10.0.16299.0\\ucrt\\x64" "-libpath:C:\\Program Files (x86)\\Windows Kits\\10\\Lib\\10.0.16299.0\\um\\x64" -nologo --start-group "..\\..\\..\\bin.v2\\libs\\hello_boost_test\\test\\hello_boost_test.test\\clang-gnu-linux-6.0.0\\release\\address-model-64\\threadap i-win32\\hello_boost_test.obj" "..\\..\\..\\bin.v2\\libs\\test\\build\\clang-gnu-linux-6.0.0\\release\\address-model-64\\link-static\\threadapi-win32\\libboost_uni t_test_framework-clang60-x64-1_66.lib" "..\\..\\..\\bin.v2\\libs\\timer\\build\\clang-gnu-linux-6.0.0\\release\\address-model-64\\link-static\\threadapi-win32\\libboost_ti mer-clang60-x64-1_66.lib" "..\\..\\..\\bin.v2\\libs\\chrono\\build\\clang-gnu-linux-6.0.0\\release\\address-model-64\\link-static\\threadapi-win32\\libboost_c hrono-clang60-x64-1_66.lib" "..\\..\\..\\bin.v2\\libs\\system\\build\\clang-gnu-linux-6.0.0\\release\\address-model-64\\link-static\\threadapi-win32\\libboost_s ystem-clang60-x64-1_66.lib" -Bstatic -Bdynamic --end-group msvcrt.lib C:\LLVM\clang-600\LLVM\bin\lld-link: warning: ignoring unknown argument: --start-group C:\LLVM\clang-600\LLVM\bin\lld-link: warning: ignoring unknown argument: -Bstatic C:\LLVM\clang-600\LLVM\bin\lld-link: warning: ignoring unknown argument: -Bdynamic C:\LLVM\clang-600\LLVM\bin\lld-link: warning: ignoring unknown argument: --end-group C:\LLVM\clang-600\LLVM\bin\lld-link: error: entry point must be defined clang++.exe: error: linker command failed with exit code 1 (use -v to see invocation) Which leaves me baffled. Verbose logs are attached, and I have several others if any kind soul would be willing to pass a more expert eye over them. Ideas on what I am doing wrong most welcome? Thanks. Paul PS I am away for a while, but eagerly await solutions on my return ;-) --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830

1 0

Permission to merge bugfix into 1.67 master (geometry)
by Barend Gehrels 30 Mar '18

30 Mar '18

Hi, Can I merge a small bugfix for Boost.Geometry into master? It is about https://github.com/boostorg/geometry/commit/68296965f55d911d74574ae7bbc0652… If allowed, I will cherry-pick this commit into master. Thanks, Barend

3 2

[gil] gcc fail with simple code
by Christian Henning 28 Mar '18

28 Mar '18

Hi all, we are, at the boost::gil corner, investigating a runtime failure when compiling with gcc 5.4. When running in release configuration the following code fails: #include <iostream> #include <boost/gil/gil_all.hpp> using namespace boost::gil; using namespace std; void error_if(bool condition) { if (condition) throw std::exception(); } bits32s c32s_min = channel_traits<bits32s>::min_value(); bits32s c32s_max = channel_traits<bits32s>::max_value(); // For channel values simply initialize the value directly template <typename ChannelValue> struct value_core { typedef ChannelValue channel_t; channel_t _min_v, _max_v; value_core() : _min_v(channel_traits<ChannelValue>::min_value()), _max_v(channel_traits<ChannelValue>::max_value()) {} }; int main(int argc, char *argv[]) { value_core<bits32s> a; bits32s v_min, v_max; v_min = channel_convert<bits32s>(c32s_min); v_max = channel_convert<bits32s>(c32s_max); //std::cout << v_min << std::endl; // std::cout << this->_min_v << std::endl; //std::cout << v_max << std::endl; // std::cout << this->_max_v << std::endl; error_if(v_min != a._min_v || v_max != a._max_v); } The interesting thing is that everything works with the cout's enabled. Has anyone ever dealt with a similar issue? Thanks, Christian

5 8

[optional] get() misses optional r-value overload in contrast to operator* and value()
by Viktor Sehr 28 Mar '18

28 Mar '18

Both *value()* and *operator** has an overload to handle if the *optional<T>* object is an r-value. However *get()* does not have the r-value overload. This leads to undefined behavior using *get()*, but not with *operator** and *value()*, in the following example: auto func0() { return optional<int>{3}; } auto func1() { const auto& x = func0().get(); // Undefined behavior const auto& y = func0().value(); // Correct const auto& z = *func0(); // Correct } Is this intended, I can't see any reason why the r-value overload of .get() would be missing? Otherwise, the following overload of .get() should be added: reference_type_of_temporary_wrapper get() && { BOOST_ASSERT(this->is_initialized()); return boost::move(this->get_impl()); } /Viktor Sehr, Software Developer at Toppluva

5 15

Unescaped special character in argument <cxx, flags>/std:c++nn
by Edward Diener 27 Mar '18

27 Mar '18

When compiling with vc++ and specifying in my user_config.jam file: using msvc : 14.1c14 : : <cxxflags>/std:c++14 ; using msvc : 14.1c17 : : <cxxflags>/std:c++latest ; I am getting the messages: user-config.jam:5: Unescaped special character in argument <cxxflags>/std:c++14 user-config.jam:6: Unescaped special character in argument <cxxflags>/std:c++latest I am using the latest 'develop' branch of Boost Build. What is the workaround for this ?

3 3

Stale branch removal - safe?
by James E. King, III 26 Mar '18

26 Mar '18

There are some stale branches (over 7 years old) from the svn conversion in the Boost.Uuid (and other) repository: https://github.com/boostorg/uuid/branches/stale Is it safe to remove these? example name: svn-branches/units/autoprefix Apart from "master" and "develop" branches and all the version tags, is anything else sacred for branches or tags? Thanks, Jim

1 0

Permission to merge into 1.67.0 (build fix)
by James E. King, III 26 Mar '18

26 Mar '18

Requesting permission to merge into 1.67.0 (build fix) pending successful CI completion of a pull request. Build script issue reported by a consumer of Boost.Uuid: https://github.com/boostorg/uuid/pull/62 Thanks, Jim

1 0

[release] Boost 1.67.0 Beta 1
by Daniel James 26 Mar '18

26 Mar '18

Boost release 1.67.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.67.0.beta.1/source/> The SHA256 checksums are as follows: 154cf490da858fd9c2307bb904b07a42cbe8355ecf99d5477f0d843c6d03cdda boost_1_67_0_b1.7z 0d854b208fefaeb5837d6c417f505b189275e32d017f6226001fb165a5ac51ed boost_1_67_0_b1.tar.bz2 6eb3f9ca8db355765f41361e1e26976228f0c2dff400aade8a5e97aec6aa59f4 boost_1_67_0_b1.tar.gz 678a6459f2517932536ec97297be1de46ea073f2e2ee17ec8397b80aa0953f49 boost_1_67_0_b1.zip For details of what's in the release, see <http://www.boost.org/users/history/version_1_67_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

6 11