Re: [Boost-users] Boost 1.65.0 Release Candidate 4

These are my results on building Boost 1.65.0 RC4 on the various platforms I’m interested in: Build platform: Fedora 26 Workstation x86_64 Build toolset: GCC 7.1 Language mode: c++11 Bootstrap command: ./bootstrap.sh –prefix=/home/dev3rd/boost_1_65_0 Build command: ./b2 link=shared runtime-link=shared address-model=64 threading=multi variant=release cxxflags="-std=c++11" install Build result: Success Build platform: Fedora 26 Workstation x86_64 Build toolset: GCC 7.1 Language mode: c++14 Bootstrap command: ./bootstrap.sh –prefix=/home/dev3rd/boost_1_65_0 Build command: ./b2 link=shared runtime-link=shared address-model=64 threading=multi variant=release cxxflags="-std=c++14" install Build result: Success Build platform: Fedora 26 Workstation x86_64 Build toolset: GCC 7.1 Language mode: c++1z Bootstrap command: ./bootstrap.sh –prefix=/home/dev3rd/boost_1_65_0 Build command: ./b2 link=shared runtime-link=shared address-model=64 threading=multi variant=release cxxflags="-std=c++1z" install Build result: Success Build platform: Windows 7 Pro 64-bit Build toolset: Visual Studio 2017 (Community edition) Language mode: default Bootstrap command: .\bootstrap.bat msvc (Why the need to add msvc? If not, the bootstrap fails.) Build command: .\b2 link=shared runtime-link=shared address-model=64 threading=multi variant=release define=_HAS_AUTO_PTR_ETC install Build result: Success Build platform: Windows 7 Pro 64-bit Build toolset: Visual Studio 2017 (Community edition) Language mode: c++14 Bootstrap command: .\bootstrap.bat msvc (Why the need to add msvc? If not, the bootstrap fails.) Build command: .\b2 link=shared runtime-link=shared address-model=64 threading=multi variant=release cxxflags="/std:c++14" define=_HAS_AUTO_PTR_ETC install Build result: Success Build platform: Windows 7 Pro 64-bit Build toolset: Visual Studio 2017 (Community edition) Language mode: c++latest Bootstrap command: .\b2 link=shared runtime-link=shared address-model=64 threading=multi variant=release cxxflags="/std:c++latest" define=_HAS_AUTO_PTR_ETC install Build result: Success Build platform: Solaris 11.3 x86_64 (No Oracle support) Build toolset: Developer Studio 12.6 (No Oracle support) Language mode: c++11 Bootstrap command: ./bootstrap.sh --prefix=/export/home/dev3rd/boost_1_65_0 --with-toolset=sun Build command: ./b2 link=shared runtime-link=shared address-model=64 threading=multi variant=release cxxflags="-std=c++11" linkflags="-std=c++11" install Build result: Unsuccessful (Too many errors to enumerate, refer to attachment boost-devel-sol11i-c++11.zip which is a capture of the whole screen output of b2.) Build platform: Solaris 11.3 x86_64 (No Oracle support) Build toolset: Developer Studio 12.6 (No Oracle support) Language mode: c++14 Bootstrap command: ./bootstrap.sh --prefix=/export/home/dev3rd/boost_1_65_0 --with-toolset=sun Build command: ./b2 link=shared runtime-link=shared address-model=64 threading=multi variant=release cxxflags="-std=c++14" linkflags="-std=c++14" install Build result: Unsuccessful (Too many errors to enumerate, refer to attachment boost-devel-sol11i-c++14.zip which is a capture of the whole screen output of b2.) Note: Oracle has acknowledged that the message “>> Assertion: (../lnk/initializer.cc, line 1865)” is the result of a compiler fault. The Boost.Optional and Boost.Python issues I have not been able to resolve. What I have learned from building Boost 1.65.0 RC4: 1. The invocation of bootstrap on Windows has slightly changed. 2. The Boost.Log and Boost.Optional issues I got from the c++14 mode build on Solaris are identical to the issues I saw when building Boost 1.64.0 but the Boost.Python issues are different. From: Marshall Clow via Boost-users Sent: Thursday, August 17, 2017 10:00 AM To: boost-users@lists.boost.org Cc: Marshall Clow Subject: [Boost-users] Boost 1.65.0 Release Candidate 4 The fourth (and hopefully final) release candidates for the 1.65.0 release are now available at: https://dl.bintray.com/boostorg/release/1.65.0/source/ [ Note: The RC1s/RC2s/RC3s are in that directory, too - make sure you get the right files! ] Changes since RC3: * Fix a bug in Boost.Thread where timed waits were waiting for a very long time. Changes since RC2: * Fix a crashing bug in Boost.ASIO * Fix a compilation error when including both and * An update to Boost.Spirit to fix compilation errors on Mac OS with -std=c++17 Changes since RC1: * An update to Boost.Config so that the flags BOOST_NO_CXX98_RANDOM_SHUFFLE and BOOST_NO_CXX98_BINDERS are now set appropriately for libc++. (This fixes the compilation errors for Boost.Test) * An update to Boost.Fiber to fix compilation errors * An update to Boost.Wave to fix compilation errors on Mac OS with -std=c++17 The SHA256 checksums are as follows: 5d255d1ff8460d52dffcf9a9b55d908ae704027a66c590ec774096effaea26c1 boost_1_65_0_rc4.7z 911602d830ea5d16483d1e565b9859d120d03f2e5176017226ef391eb9d17fc8 boost_1_65_0_rc4.tar.bz2 369e06dc787d32b0fbaae020f33d814c9e7b77263acb859776968e623035f760 boost_1_65_0_rc4.tar.gz a9c6b8346b05ea43ac4278e80036a9e956ea99fc61f0b7f55469471af2df934c boost_1_65_0_rc4.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. Thanks! -- The release managers -------------------------------------------------------------------------------- _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users