[release] Boost 1.69.0 Beta 1 Release Candidate 2
The release candidates for the second 1.69.0 beta release are now available at: https://dl.bintray.com/boostorg/beta/1.69.0.beta1.rc2/source/ The release notes are not yet final. The SHA256 checksums are as follows: 77827b25121159a4e65cfbdf19713e2d589fce267fd6f08615a453d24753c9d3 ./boost_1_69_0_b1_rc2.7z ea05c6e01c856369afdab1f6c075e06fb0f965ab1c247f753ed5c951a9db4e71 ./boost_1_69_0_b1_rc2.tar.bz2 b393a73cf084be716c40ef346cfacb1c95e7b14637e8385eeeb50774dd0b99ed ./boost_1_69_0_b1_rc2.tar.gz 74c0c0a19a700fee2b4f434bb7df50840642e3c35924e85864b278bd519af062 ./boost_1_69_0_b1_rc2.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. -- The Boost Release Managers
On Wed, Nov 14, 2018 at 2:50 PM Marshall Clow
The release candidates for the second 1.69.0 beta release are now available at:
https://dl.bintray.com/boostorg/beta/1.69.0.beta1.rc2/source/
The release notes are not yet final. 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.
TL;DR - same results as RC1 I have built the RC on Mac OS X 10.11 using Apple LLVM version 8.0.0 (clang-800.0.42.1) successfully while specifying c++03/11/14/1z I have built the RC on Mac OS X 10.13 using Apple LLVM version 10.0.0 (clang-1000.10.44.4) successfully while specifying c++03/11/14, but failed when specifying c++17/2a, because the Python 2.7 headers shipped with Mac OS 10.13 use the "register" keyword: In file included from /System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/Python.h:85: /System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/unicodeobject.h:534:5: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister] register PyObject *obj, /* Object */ ^~~~~~~~~ I have built the RC on Mac OS X 10.13 using a recent trunk build of clang (version 8.0.0 (trunk 346609)) successfully while specifying c++03/11/14, but failed when specifying c++17/2a, because the Python 2.7 headers shipped with Mac OS 10.13 use the "register" keyword: In file included from /System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/Python.h:85: /System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/unicodeobject.h:534:5: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister] register PyObject *obj, /* Object */ ^~~~~~~~~ (same results as with Apple's clang) -- Marshall
On Thu, 15 Nov 2018 at 00:50, Marshall Clow via Boost
The release candidates for the second 1.69.0 beta release are now available at:
https://dl.bintray.com/boostorg/beta/1.69.0.beta1.rc2/source/
The release notes are not yet final.
The SHA256 checksums are as follows:
77827b25121159a4e65cfbdf19713e2d589fce267fd6f08615a453d24753c9d3 ./boost_1_69_0_b1_rc2.7z ea05c6e01c856369afdab1f6c075e06fb0f965ab1c247f753ed5c951a9db4e71 ./boost_1_69_0_b1_rc2.tar.bz2 b393a73cf084be716c40ef346cfacb1c95e7b14637e8385eeeb50774dd0b99ed ./boost_1_69_0_b1_rc2.tar.gz 74c0c0a19a700fee2b4f434bb7df50840642e3c35924e85864b278bd519af062 ./boost_1_69_0_b1_rc2.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.
I have tried to build with VC-15.9 (yesterday's update) and I hit the following: don't know how to make
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\vcvarsall.bat ...skipped pc:\boost-build\boost\bin.v2\standalone\msvc\msvc-15.9msvc-setup.read for lack of
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\vcvarsall.bat... common.mkdir c:\boost-build\boost after which everything fails of course, which is unsurprising as vcvarsall.bat is now located at "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat" I don't know why, how or what, but that's what I see. b2 builds, but that's because I'm building from a dev-prompt. Clang also fails [using lld-link.exe] as apparently Peter's fixes are not merged to master [yet]. I presume the above issue will rear its head as well, after that as this appears to be unrelated to boost. degski -- *“If something cannot go on forever, it will stop" - Herbert Stein*
On Wed, Nov 14, 2018 at 11:12 PM degski
On Thu, 15 Nov 2018 at 00:50, Marshall Clow via Boost < boost@lists.boost.org> wrote:
The release candidates for the second 1.69.0 beta release are now available at:
https://dl.bintray.com/boostorg/beta/1.69.0.beta1.rc2/source/
The release notes are not yet final.
The SHA256 checksums are as follows:
77827b25121159a4e65cfbdf19713e2d589fce267fd6f08615a453d24753c9d3 ./boost_1_69_0_b1_rc2.7z ea05c6e01c856369afdab1f6c075e06fb0f965ab1c247f753ed5c951a9db4e71 ./boost_1_69_0_b1_rc2.tar.bz2 b393a73cf084be716c40ef346cfacb1c95e7b14637e8385eeeb50774dd0b99ed ./boost_1_69_0_b1_rc2.tar.gz 74c0c0a19a700fee2b4f434bb7df50840642e3c35924e85864b278bd519af062 ./boost_1_69_0_b1_rc2.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.
I have tried to build with VC-15.9 (yesterday's update) and I hit the following:
don't know how to make
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\vcvarsall.bat ...skipped pc:\boost-build\boost\bin.v2\standalone\msvc\msvc-15.9msvc-setup.read for lack of
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\vcvarsall.bat... common.mkdir c:\boost-build\boost
after which everything fails of course, which is unsurprising as vcvarsall.bat is now located at "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat"
I don't know why, how or what, but that's what I see. b2 builds, but that's because I'm building from a dev-prompt.
Short answer - I don't care about this for the beta. (since the MSVC update happened yesterday), but it ought to be fixed for the 1.69.0 release. -- Marshall
On Thu, 15 Nov 2018 at 20:48, Marshall Clow
On Wed, Nov 14, 2018 at 11:12 PM degski
wrote: On Thu, 15 Nov 2018 at 00:50, Marshall Clow via Boost < boost@lists.boost.org> wrote:
The release candidates for the second 1.69.0 beta release are now available at:
https://dl.bintray.com/boostorg/beta/1.69.0.beta1.rc2/source/
The release notes are not yet final.
The SHA256 checksums are as follows:
77827b25121159a4e65cfbdf19713e2d589fce267fd6f08615a453d24753c9d3 ./boost_1_69_0_b1_rc2.7z ea05c6e01c856369afdab1f6c075e06fb0f965ab1c247f753ed5c951a9db4e71 ./boost_1_69_0_b1_rc2.tar.bz2 b393a73cf084be716c40ef346cfacb1c95e7b14637e8385eeeb50774dd0b99ed ./boost_1_69_0_b1_rc2.tar.gz 74c0c0a19a700fee2b4f434bb7df50840642e3c35924e85864b278bd519af062 ./boost_1_69_0_b1_rc2.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.
I have tried to build with VC-15.9 (yesterday's update) and I hit the following:
don't know how to make
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\vcvarsall.bat ...skipped pc:\boost-build\boost\bin.v2\standalone\msvc\msvc-15.9msvc-setup.read for lack of
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\vcvarsall.bat... common.mkdir c:\boost-build\boost
after which everything fails of course, which is unsurprising as vcvarsall.bat is now located at "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat"
I don't know why, how or what, but that's what I see. b2 builds, but that's because I'm building from a dev-prompt.
Short answer - I don't care about this for the beta. (since the MSVC update happened yesterday), but it ought to be fixed for the 1.69.0 release.
I understand [that you don't care about something that happened the day before]. Would indeed be nice to have it fixed, 15.9 is quite an update and from what I understood from STL on reddit, the base for VC-16 (VS2019). degski -- *“If something cannot go on forever, it will stop" - Herbert Stein*
On Wed, Nov 14, 2018 at 11:12 PM degski
On Thu, 15 Nov 2018 at 00:50, Marshall Clow via Boost < boost@lists.boost.org> wrote:
The release candidates for the second 1.69.0 beta release are now available at:
https://dl.bintray.com/boostorg/beta/1.69.0.beta1.rc2/source/
The release notes are not yet final.
The SHA256 checksums are as follows:
77827b25121159a4e65cfbdf19713e2d589fce267fd6f08615a453d24753c9d3 ./boost_1_69_0_b1_rc2.7z ea05c6e01c856369afdab1f6c075e06fb0f965ab1c247f753ed5c951a9db4e71 ./boost_1_69_0_b1_rc2.tar.bz2 b393a73cf084be716c40ef346cfacb1c95e7b14637e8385eeeb50774dd0b99ed ./boost_1_69_0_b1_rc2.tar.gz 74c0c0a19a700fee2b4f434bb7df50840642e3c35924e85864b278bd519af062 ./boost_1_69_0_b1_rc2.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.
I have tried to build with VC-15.9 (yesterday's update) and I hit the following:
don't know how to make
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\vcvarsall.bat ...skipped pc:\boost-build\boost\bin.v2\standalone\msvc\msvc-15.9msvc-setup.read for lack of
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\vcvarsall.bat... common.mkdir c:\boost-build\boost
after which everything fails of course, which is unsurprising as vcvarsall.bat is now located at "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat"
That was abrupt; sorry. Thanks for the bug report. We need to look into it, and get it fixed for the upcoming 1.69.0 release - just not for the beta. -- Marshall
participants (2)
-
degski
-
Marshall Clow