[release] Boost 1.70.0 Beta 1 Release Candidate 1
The release candidates for the first 1.70.0 beta release are now available at: https://dl.bintray.com/boostorg/beta/1.70.0.beta.1.rc1/source/ The release notes are not yet available. The SHA256 checksums are as follows: a7c570d6307d05dc8d45a3b4c69a0afdcba2b22eac0c4da4d496559f53db7b89 ./boost_1_70_0_b1_rc1.7z 4b91b9a203cf12f6001cf39de83c7cc005fbc5390e2b4b2fc29ce7b19c0537a7 ./boost_1_70_0_b1_rc1.tar.bz2 460dd6499bba9df04c6bfa219b26097bad803b8758304ba45f2fc291aa42c96e ./boost_1_70_0_b1_rc1.tar.gz f209c9a086ed2c7882a0bc8755792f436eb141eaeb8c823ed57295ca9ce25b93 ./boost_1_70_0_b1_rc1.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
-----Original Message----- From: Boost
On Behalf Of Marshall Clow via Boost Sent: Friday, March 8, 2019 7:22 PM The release candidates for the first 1.70.0 beta release are now available at:
https://dl.bintray.com/boostorg/beta/1.70.0.beta.1.rc1/source/
The release notes are not yet available.
The SHA256 checksums are as follows:
a7c570d6307d05dc8d45a3b4c69a0afdcba2b22eac0c4da4d496559f53db7b89 ./boost_1_70_0_b1_rc1.7z 4b91b9a203cf12f6001cf39de83c7cc005fbc5390e2b4b2fc29ce7b19c0537a7 ./boost_1_70_0_b1_rc1.tar.bz2 460dd6499bba9df04c6bfa219b26097bad803b8758304ba45f2fc291aa42c96e ./boost_1_70_0_b1_rc1.tar.gz f209c9a086ed2c7882a0bc8755792f436eb141eaeb8c823ed57295ca9ce25b93 ./boost_1_70_0_b1_rc1.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've run the plain .\bootstrap.bat + .\b2 on win10 x64 with VS2017 (v15.9.6). That compiled with a few warnings, but no errors. However, when trying to run b2 from within the status directory, I get the following error: error: Unable to find file or target named error: '/C:/Users/<user-name>/Downloads/boost_1_70_0_b1_rc1/boost_1_70_0/libs/predef/test//C:\Users\<user-name>\Downloads\boost_1_70_0_b1_rc1\boost_1_70_0\libs\predef\include/boost/predef.h' error: referred to from project at error: '.' Best Mike
On Fri, Mar 8, 2019 at 12:25 PM
I've run the plain .\bootstrap.bat + .\b2 on win10 x64 with VS2017 (v15.9.6).
That compiled with a few warnings, but no errors. However, when trying to run b2 from within the status directory, I get the following error:
error: Unable to find file or target named error: '/C:/Users/<user-name>/Downloads/boost_1_70_0_b1_rc1/boost_1_70_0/libs/predef/test//C:\Users\<user-name>\Downloads\boost_1_70_0_b1_rc1\boost_1_70_0\libs\predef\include/boost/predef.h' error: referred to from project at error: '.'
I am seeing the same problem on Ubuntu w/gcc 7.3.2: error: Unable to find file or target named error: '/Sources/Boost/smoke/boost_1_70_0/libs/predef/include/boost/predef.h' error: referred to from project at error: '../libs/predef/test' -- Marshall
On Fri, Mar 8, 2019 at 2:50 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:
On Fri, Mar 8, 2019 at 12:25 PM
wrote: I've run the plain .\bootstrap.bat + .\b2 on win10 x64 with VS2017 (v15.9.6).
That compiled with a few warnings, but no errors. However, when trying to run b2 from within the status directory, I get the following error:
error: Unable to find file or target named error:
'/C:/Users/<user-name>/Downloads/boost_1_70_0_b1_rc1/boost_1_70_0/libs/predef/test//C:\Users\<user-name>\Downloads\boost_1_70_0_b1_rc1\boost_1_70_0\libs\predef\include/boost/predef.h'
error: referred to from project at error: '.'
I am seeing the same problem on Ubuntu w/gcc 7.3.2:
error: Unable to find file or target named error: '/Sources/Boost/smoke/boost_1_70_0/libs/predef/include/boost/predef.h' error: referred to from project at error: '../libs/predef/test'
Grumble :-( I'll investigate. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net
On Fri, Mar 8, 2019 at 1:11 PM Rene Rivera
On Fri, Mar 8, 2019 at 2:50 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:
On Fri, Mar 8, 2019 at 12:25 PM
wrote: I've run the plain .\bootstrap.bat + .\b2 on win10 x64 with VS2017 (v15.9.6).
That compiled with a few warnings, but no errors. However, when trying to run b2 from within the status directory, I get the following error:
error: Unable to find file or target named error:
'/C:/Users/<user-name>/Downloads/boost_1_70_0_b1_rc1/boost_1_70_0/libs/predef/test//C:\Users\<user-name>\Downloads\boost_1_70_0_b1_rc1\boost_1_70_0\libs\predef\include/boost/predef.h'
error: referred to from project at error: '.'
I am seeing the same problem on Ubuntu w/gcc 7.3.2:
error: Unable to find file or target named error: '/Sources/Boost/smoke/boost_1_70_0/libs/predef/include/boost/predef.h' error: referred to from project at error: '../libs/predef/test'
Grumble :-( I'll investigate.
Most of the tests for predef are passing: https://www.boost.org/development/tests/master/developer/predef.html --- Marshall
On Fri, Mar 8, 2019 at 12:50 PM Marshall Clow
On Fri, Mar 8, 2019 at 12:25 PM
wrote: I've run the plain .\bootstrap.bat + .\b2 on win10 x64 with VS2017 (v15.9.6).
That compiled with a few warnings, but no errors. However, when trying to run b2 from within the status directory, I get the following error:
error: Unable to find file or target named error: '/C:/Users/<user-name>/Downloads/boost_1_70_0_b1_rc1/boost_1_70_0/libs/predef/test//C:\Users\<user-name>\Downloads\boost_1_70_0_b1_rc1\boost_1_70_0\libs\predef\include/boost/predef.h' error: referred to from project at error: '.'
I am seeing the same problem on Ubuntu w/gcc 7.3.2:
error: Unable to find file or target named error: '/Sources/Boost/smoke/boost_1_70_0/libs/predef/include/boost/predef.h' error: referred to from project at error: '../libs/predef/test'
It appears that the `include` directory is missing from `libs/predef`. It also appears that predef is not the only library that this has happened to. -- Marshall
On Fri, Mar 8, 2019 at 1:37 PM Marshall Clow
On Fri, Mar 8, 2019 at 12:50 PM Marshall Clow
wrote: On Fri, Mar 8, 2019 at 12:25 PM
wrote: I've run the plain .\bootstrap.bat + .\b2 on win10 x64 with VS2017 (v15.9.6).
That compiled with a few warnings, but no errors. However, when trying to run b2 from within the status directory, I get the following error:
error: Unable to find file or target named error: '/C:/Users/<user-name>/Downloads/boost_1_70_0_b1_rc1/boost_1_70_0/libs/predef/test//C:\Users\<user-name>\Downloads\boost_1_70_0_b1_rc1\boost_1_70_0\libs\predef\include/boost/predef.h' error: referred to from project at error: '.'
I am seeing the same problem on Ubuntu w/gcc 7.3.2:
error: Unable to find file or target named error: '/Sources/Boost/smoke/boost_1_70_0/libs/predef/include/boost/predef.h' error: referred to from project at error: '../libs/predef/test'
It appears that the `include` directory is missing from `libs/predef`. It also appears that predef is not the only library that this has happened to.
The lack of an `include` directory turns out to not be the problem. -- Marshall
On Fri, Mar 8, 2019 at 4:04 PM Marshall Clow
On Fri, Mar 8, 2019 at 1:37 PM Marshall Clow
wrote: On Fri, Mar 8, 2019 at 12:50 PM Marshall Clow
wrote: On Fri, Mar 8, 2019 at 12:25 PM
wrote: I've run the plain .\bootstrap.bat + .\b2 on win10 x64 with VS2017 (v15.9.6).
That compiled with a few warnings, but no errors. However, when trying to run b2 from within the status directory, I get the following error:
error: Unable to find file or target named error: '/C:/Users/<user-name>/Downloads/boost_1_70_0_b1_rc1/boost_1_70_0/libs/predef/test//C:\Users\<user-name>\Downloads\boost_1_70_0_b1_rc1\boost_1_70_0\libs\predef\include/boost/predef.h' error: referred to from project at error: '.'
I am seeing the same problem on Ubuntu w/gcc 7.3.2:
error: Unable to find file or target named error: '/Sources/Boost/smoke/boost_1_70_0/libs/predef/include/boost/predef.h' error: referred to from project at error: '../libs/predef/test'
It appears that the `include` directory is missing from `libs/predef`. It also appears that predef is not the only library that this has happened to.
The lack of an `include` directory turns out to not be the problem.
It's by "design".. as in that's the way the monolithic release structure works. It's a problem with my Predef jamfiles. Which I though I had dealt with.. But well I guess I didn't :-( -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net
On Fri, Mar 8, 2019 at 10:21 AM Marshall Clow
The release candidates for the first 1.70.0 beta release are now available at:
https://dl.bintray.com/boostorg/beta/1.70.0.beta.1.rc1/source/
The release notes are not yet available.
The SHA256 checksums are as follows:
a7c570d6307d05dc8d45a3b4c69a0afdcba2b22eac0c4da4d496559f53db7b89 ./boost_1_70_0_b1_rc1.7z 4b91b9a203cf12f6001cf39de83c7cc005fbc5390e2b4b2fc29ce7b19c0537a7 ./boost_1_70_0_b1_rc1.tar.bz2 460dd6499bba9df04c6bfa219b26097bad803b8758304ba45f2fc291aa42c96e ./boost_1_70_0_b1_rc1.tar.gz f209c9a086ed2c7882a0bc8755792f436eb141eaeb8c823ed57295ca9ce25b93 ./boost_1_70_0_b1_rc1.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 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.14 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.14 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.14 using a recent trunk build of clang (version 9.0.0 (https://github.com/llvm/llvm-project.git 881e83d8b94f1997de674ed8ff382a73a29a719d)) 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) I have built the RC on Ubuntu 18.14 with gcc 7.3.2 successfully while specifying c++03/11/14, but failed when specifying c++17/2a, because the Python 2.7 headers shipped with 18.04 use the "register" keyword: In file included from /usr/include/python2.7/Python.h:88: /usr/include/python2.7/unicodeobject.h:534:5: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register] register PyObject *obj, /* Object */ ^~~~~~~~~ and I had the same results with a recently built version of clang on Ubuntu (success on 03/11/14, but python failures with 17/2a) -- Marshall
On Fri, Mar 8, 2019 at 6:42 PM Marshall Clow via Boost-users < boost-users@lists.boost.org> wrote:
On Fri, Mar 8, 2019 at 10:21 AM Marshall Clow
wrote: The release candidates for the first 1.70.0 beta release are now available at:
https://dl.bintray.com/boostorg/beta/1.70.0.beta.1.rc1/source/
The release notes are not yet available.
The SHA256 checksums are as follows:
a7c570d6307d05dc8d45a3b4c69a0afdcba2b22eac0c4da4d496559f53db7b89 ./boost_1_70_0_b1_rc1.7z 4b91b9a203cf12f6001cf39de83c7cc005fbc5390e2b4b2fc29ce7b19c0537a7 ./boost_1_70_0_b1_rc1.tar.bz2 460dd6499bba9df04c6bfa219b26097bad803b8758304ba45f2fc291aa42c96e ./boost_1_70_0_b1_rc1.tar.gz f209c9a086ed2c7882a0bc8755792f436eb141eaeb8c823ed57295ca9ce25b93 ./boost_1_70_0_b1_rc1.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 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.14 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.14 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.14 using a recent trunk build of clang (version 9.0.0 (https://github.com/llvm/llvm-project.git 881e83d8b94f1997de674ed8ff382a73a29a719d)) 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)
I have built the RC on Ubuntu 18.14 with gcc 7.3.2 successfully while specifying c++03/11/14, but failed when specifying c++17/2a, because the Python 2.7 headers shipped with 18.04 use the "register" keyword:
In file included from /usr/include/python2.7/Python.h:88: /usr/include/python2.7/unicodeobject.h:534:5: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register] register PyObject *obj, /* Object */ ^~~~~~~~~
and I had the same results with a recently built version of clang on Ubuntu (success on 03/11/14, but python failures with 17/2a)
I encountered similar issues when trying to build python with modern versions of visual studio. I ended up making the decision [1] that msvc-14.0 would build against python 3.x while earlier versions would remain on python 2.7. Since python 2.X is going end of life at the end of the year [2], I'm thinking that I'm going to drop windows builds with boost python for the older compilers after that point. You're obviously free to test against whatever config you like, just wanted to mention that. Tom [1] https://lists.boost.org/Archives/boost/2018/07/242443.php [2] https://pythonclock.org/
participants (4)
-
Marshall Clow
-
mike.dev@gmx.de
-
Rene Rivera
-
Tom Kent