[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 <mclow.lists@gmail.com> 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. 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 <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 <p/C:/boost>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.9>msvc-setup.read for lack of <p/C:/boost>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 <degski@gmail.com> 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 <p/C:/boost>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.9>msvc-setup.read for lack of <p/C:/boost>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 <mclow.lists@gmail.com> wrote:
On Wed, Nov 14, 2018 at 11:12 PM degski <degski@gmail.com> 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 <p/C:/boost>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.9>msvc-setup.read for lack of <p/C:/boost>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*
degski wrote:
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).
FWIW, latest msvc-14.1 works for me, on both master and develop.
On Fri, 16 Nov 2018 at 14:41, Peter Dimov via Boost <boost@lists.boost.org> wrote:
degski wrote:
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).
FWIW, latest msvc-14.1 works for me, on both master and develop.
Did you upgrade from VS2015 [or have a side-by-side install (15 and 17)? I have seen that artefacts of VS2015 "make things work", while they do not, iff using a clean install of VS2017 (which is what I have). F.e. the old style clang integration [before it was removed with the 7.0.0 release, to be replaced with the plugin] kept on working as well, only to break on a clean install. The referenced file [vcvarsall.bat] does simply not exist in that location. degski -- *“If something cannot go on forever, it will stop" - Herbert Stein*
On Fri, Nov 16, 2018, 12:05 AM degski via Boost <boost@lists.boost.org wrote:
On Thu, 15 Nov 2018 at 20:48, Marshall Clow <mclow.lists@gmail.com> wrote:
On Wed, Nov 14, 2018 at 11:12 PM degski <degski@gmail.com> 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 <p/C:/boost>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.9>msvc-setup.read for lack of <p/C:/boost>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).
I was able to build with 15.9 without any issues. See the end of the log here: https://gist.github.com/teeks99/b59b073cdf08f08d5fd6d170721c92ca That was an upgrade from 15.8, on a machine with other versions of VS....could either of those things be mitigating factors? Tom
On 11/16/2018 7:20 AM, Tom Kent via Boost wrote:
On Fri, Nov 16, 2018, 12:05 AM degski via Boost <boost@lists.boost.org wrote:
On Thu, 15 Nov 2018 at 20:48, Marshall Clow <mclow.lists@gmail.com> wrote:
On Wed, Nov 14, 2018 at 11:12 PM degski <degski@gmail.com> 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 <p/C:/boost>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.9>msvc-setup.read for lack of <p/C:/boost>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).
I was able to build with 15.9 without any issues. See the end of the log here: https://gist.github.com/teeks99/b59b073cdf08f08d5fd6d170721c92ca
That was an upgrade from 15.8, on a machine with other versions of VS....could either of those things be mitigating factors?
I am thinking probably not. The file and directory locations for the Visual Studio 2017 versions (e.g. compiler 14.1) are totally different than the older releases. So all here know, there is already an update to the Visual Studio 15.9.0 to 15.9.1. The size of the update is on the order of 4 GB. I have no idea what makes it so large. The official release notes are not giving a whole lot of guidance for the download size increase. Also, after applying the 15.9.1 in the last ten minutes, I have to restart my computer. Almost all previous Visual Studio updates do not require this. Sincerely, Robert
Tom
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Robert via Boost Sent: 16 November 2018 16:33 To: boost@lists.boost.org Cc: Robert Subject: Re: [boost] [release] Boost 1.69.0 Beta 1 Release Candidate 2
On 11/16/2018 7:20 AM, Tom Kent via Boost wrote:
On Fri, Nov 16, 2018, 12:05 AM degski via Boost <boost@lists.boost.org wrote:
On Thu, 15 Nov 2018 at 20:48, Marshall Clow <mclow.lists@gmail.com> wrote:
On Wed, Nov 14, 2018 at 11:12 PM degski <degski@gmail.com> 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 <p/C:/boost>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.9>msvc-setup.read for lack of <p/C:/boost>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).
I was able to build with 15.9 without any issues. See the end of the log here: https://gist.github.com/teeks99/b59b073cdf08f08d5fd6d170721c92ca
That was an upgrade from 15.8, on a machine with other versions of VS....could either of those things be mitigating factors?
I am thinking probably not. The file and directory locations for the Visual Studio 2017 versions (e.g. compiler 14.1) are totally different than the older releases.
So all here know, there is already an update to the Visual Studio 15.9.0 to 15.9.1. The size of the update is on the order of 4 GB. I have no idea what makes it so large. The official release notes are not giving a whole lot of guidance for the download size increase. Also, after applying the 15.9.1 in the last ten minutes, I have to restart my computer. Almost all previous Visual Studio updates do not require this.
Sincerely,
Robert
I had to go and have lunch ;-) But, FWIW, VS 15.9.1 is working OK for me, so far. Paul
On 11/16/2018 10:58 AM, Paul A. Bristow via Boost wrote:
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Robert via Boost Sent: 16 November 2018 16:33 To: boost@lists.boost.org Cc: Robert Subject: Re: [boost] [release] Boost 1.69.0 Beta 1 Release Candidate 2
On 11/16/2018 7:20 AM, Tom Kent via Boost wrote:
On Fri, Nov 16, 2018, 12:05 AM degski via Boost <boost@lists.boost.org wrote:
On Thu, 15 Nov 2018 at 20:48, Marshall Clow <mclow.lists@gmail.com> wrote:
On Wed, Nov 14, 2018 at 11:12 PM degski <degski@gmail.com> 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 <p/C:/boost>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.9>msvc-setup.read for lack of <p/C:/boost>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).
I was able to build with 15.9 without any issues. See the end of the log here: https://gist.github.com/teeks99/b59b073cdf08f08d5fd6d170721c92ca
That was an upgrade from 15.8, on a machine with other versions of VS....could either of those things be mitigating factors?
I am thinking probably not. The file and directory locations for the Visual Studio 2017 versions (e.g. compiler 14.1) are totally different than the older releases.
So all here know, there is already an update to the Visual Studio 15.9.0 to 15.9.1. The size of the update is on the order of 4 GB. I have no idea what makes it so large. The official release notes are not giving a whole lot of guidance for the download size increase. Also, after applying the 15.9.1 in the last ten minutes, I have to restart my computer. Almost all previous Visual Studio updates do not require this.
Sincerely,
Robert
I had to go and have lunch ;-)
But, FWIW, VS 15.9.1 is working OK for me, so far.
Paul
I am currently building the production product in Release | x64. It is about 55% complete and no errors. Sometimes a new VS update causes unexpected compiler errors on the existing source. If I have bad results, I will post again. Sincerely, Robert
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Fri, 16 Nov 2018 at 18:33, Robert via Boost <boost@lists.boost.org> wrote:
So all here know, there is already an update to the Visual Studio 15.9.0 to 15.9.1.
Holy moly, talk about vaporware. The release notes <https://docs.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes#15.9.1> only mention a fix for xbox. I'll give it a spin and report back. degski -- *“If something cannot go on forever, it will stop" - Herbert Stein*
On Fri, 16 Nov 2018 at 15:20, Tom Kent via Boost <boost@lists.boost.org> wrote:
That was an upgrade from 15.8, on a machine with other versions of VS....could either of those things be mitigating factors?
Sorry, going thru the posts in order, yes, I think that is the case [other versions mitigating the problem]. I doubt there's anyting wrong with my install as it works perfectly fine, the dev-prompt works fine and also vcpkg has no trouble [I did not have to rebuild boost, so that might break as well, when I do need to do that]. degski -- *“If something cannot go on forever, it will stop" - Herbert Stein*
On Fri, Nov 16, 2018 at 2:20 PM Tom Kent via Boost <boost@lists.boost.org> wrote:
I was able to build with 15.9 without any issues. See the end of the log here: https://gist.github.com/teeks99/b59b073cdf08f08d5fd6d170721c92ca
That was an upgrade from 15.8, on a machine with other versions of VS....could either of those things be mitigating factors?
15.9 on a fresh W10 setup works fine as well.. -- Olaf
On Sat, 17 Nov 2018 at 12:00, Olaf van der Spek via Boost < boost@lists.boost.org> wrote:
On Fri, Nov 16, 2018 at 2:20 PM Tom Kent via Boost <boost@lists.boost.org> wrote:
I was able to build with 15.9 without any issues. See the end of the log here: https://gist.github.com/teeks99/b59b073cdf08f08d5fd6d170721c92ca
That was an upgrade from 15.8, on a machine with other versions of VS....could either of those things be mitigating factors?
15.9 on a fresh W10 setup works fine as well..
OK, let's approach it the other way around then, where is your vcvarsall.bat located. I presume you (re-)installed VC-15.9 on Windows-1809.107 [could you please post those specifics]? I have these <https://imgur.com/a/Im4WYcK> workloads installed. I upgraded to 15.9.1 and still (as expected) the same. Thanks in advance, degski -- *“If something cannot go on forever, it will stop" - Herbert Stein*
On Sat, Nov 17, 2018 at 11:33 AM degski <degski@gmail.com> wrote:
15.9 on a fresh W10 setup works fine as well..
OK, let's approach it the other way around then, where is your vcvarsall.bat located.
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build
I presume you (re-)installed VC-15.9 on Windows-1809.107 [could you please post those specifics]? I have these workloads installed.
About: Edition: W 10 Pro N Version: 1803 Installed on 11/11/2018 OS build: 17134.407 I think 1809 was on hold due to the file deletion issue.
I upgraded to 15.9.1 and still (as expected) the same.
Tried a clean boost directory (fresh unzip)? My workloads: https://imgur.com/a/A0UPpRp -- Olaf
On Sat, 17 Nov 2018 at 14:27, Olaf van der Spek <ml@vdspek.org> wrote:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build
Right, so you confirm that that *is* the location where vcvarsall.bat is located. So something is wrong, but it does not seem to be my install. Just a question, do you build from an ordinary prompt or from a dev-prompt? I'll try the fresh boost unzip, but it was fresh from the start, so I doubt that's gonna make a difference. degski -- *“If something cannot go on forever, it will stop" - Herbert Stein*
On Sat, 17 Nov 2018 at 14:40, degski <degski@gmail.com> wrote:
On Sat, 17 Nov 2018 at 14:27, Olaf van der Spek <ml@vdspek.org> wrote:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build
Right, so you confirm that that *is* the location where vcvarsall.bat is located. So something is wrong, but it does not seem to be my install. Just a question, do you build from an ordinary prompt or from a dev-prompt?
I'll try the fresh boost unzip, but it was fresh from the start, so I doubt that's gonna make a difference.
From an ordinary prompt:
'cl' is not recognized as an internal or external command, operable program or batch file. ...failed updating 1 target... Same thing as before from the dev-prompt. Windhoze is so much fun <https://www.reddit.com/r/Windows10/> nowadays [don't we have fun?], wtf, no, I really do need Paint3D, the bloody Photos thing (5-10 seconds to open one .jpg of small size) [Nutella said so] , the latest imoji's (really, how infantile has the world become?) and I also really like the retro-responsiveness of Edge! I hope that Gnome Build will shape up, then I'm out [30+ years Winsuck user], of to Fedora [dual booting at the moment, already getting my feet wet and I like the temperature (bar the CoC)]. degski -- *“If something cannot go on forever, it will stop" - Herbert Stein*
On Sat, Nov 17, 2018 at 1:40 PM degski <degski@gmail.com> wrote:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build
Right, so you confirm that that is the location where vcvarsall.bat is located. So something is wrong, but it does not seem to be my install. Just a question, do you build from an ordinary prompt or from a dev-prompt?
I use an ordinary cmd or ps prompt.
I'll try the fresh boost unzip, but it was fresh from the start, so I doubt that's gonna make a difference.
Hmm, does Boost (build) cache some files outside of the boost tree? -- Olaf
Progress! I got things to build again, and I've been able to reproduce the failure. I was using this as a project-jam file: import option ; using msvc : 15.9 : : <cxxflags>-DBOOST_NO_ANSI_APIS <cxxflags>-DBOOST_USE_WINAPI_VERSION=0x0A00 <cxxflags>-DBOOST_USE_WINDOWS_H=1 <cxxflags>-D_WIN32_WINNT=0x0A00 <cxxflags>-D_MT <cxxflags>-D_WIN32 <cxxflags>-DNOMINMAX <cxxflags>-DWIN32_LEAN_AND_MEAN ; option.set keep-going : false ; This gives the reported failures, but which is, as far as I can see, correct, and I've used this pjf before. Now I did what Peter said and I've used: using msvc : : : ; no more, that works. There is one weird error "not recognizing //" but it's on std::cerr apparently [only on the console], so it's hard to see where this happened as the rest goes to std::cout [and is logged to file]. So telling b2 it's Win10 gives this failure, donnu. degski -- *“If something cannot go on forever, it will stop" - Herbert Stein*
On Sat, 17 Nov 2018 at 17:17, Peter Dimov via Boost <boost@lists.boost.org> wrote:
degski wrote:
I was using this as a project-jam file:
import option ;
using msvc : 15.9 : :
...
The correct version number here is `14.1`, not 15.9.
Well, we'll have to thank MS for that, what are we talking about 14.1, 15.9.1 or 19.16 [and it's all the same thing **face-palm**, **throws up hands**]? But thanks, Peter, will give that a spin, but tomorrow. degski -- *“If something cannot go on forever, it will stop" - Herbert Stein*
On Sat, 17 Nov 2018 at 17:49, degski <degski@gmail.com> wrote:
On Sat, 17 Nov 2018 at 17:17, Peter Dimov via Boost <boost@lists.boost.org> wrote:
degski wrote:
I was using this as a project-jam file:
import option ;
using msvc : 15.9 : :
...
The correct version number here is `14.1`, not 15.9.
Well, we'll have to thank MS for that, what are we talking about 14.1, 15.9.1 or 19.16 [and it's all the same thing **face-palm**, **throws up hands**]? But thanks, Peter, will give that a spin, but tomorrow.
So, I did and the results are good [rc2], previously [1.68] not all the stack-trace libs built correctly, now they all do. Thanks Peter. And also thanks to Olaf (sorry for the Olav) as your help stopped me from searching under the lamp-post by confirming that all was good in respect of vc-install. 1809 is up now in case you missed it: https://www.microsoft.com/en-us/software-download/windows10. I think this option is more reliable, just mount the iso and run the setup file [i.e. don't use windows update nor boot from a dvd/thumb-stick]. degski -- *“If something cannot go on forever, it will stop" - Herbert Stein*
On Wed, Nov 14, 2018 at 11:12 PM degski <degski@gmail.com> 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 <p/C:/boost>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.9>msvc-setup.read for lack of <p/C:/boost>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
degski wrote:
I have tried to build with VC-15.9 (yesterday's update) and I hit the following:
don't know how to make <p/C:/boost>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\vcvarsall.bat
Try deleting the bin.v2 directory, see if that persists.
On Wed, Nov 14, 2018 at 4:50 PM 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.
We're still seeing the same msvc-8.0 errors: compile-c-c++ bin.v2\libs\log\build\msvc-8.0\release\link-static\threadapi-win32\threading-multi\trivial.obj trivial.cpp .\boost/parameter/aux_/arg_list.hpp(227) : error C2064: term does not evaluate to a function taking 1 arguments .\boost/parameter/aux_/arg_list.hpp(390) : see reference to class template instantiation 'boost::parameter::aux::arg_list<TaggedArg,Next>' being compiled toolset arch compile Link Execute msvc-8.0 32 FAIL X X msvc-8.0 64 FAIL X X msvc-9.0 32 X X X msvc-9.0 64 X X X msvc-10.0 32 X X X msvc-10.0 64 X X X msvc-11.0 32 X X X msvc-11.0 64 X X X msvc-12.0 32 X X X msvc-12.0 64 X X X msvc-14.0 32 X X X msvc-14.0 64 X X X msvc-14.1 32 X X X msvc-14.1 64 X X X Compile means that the b2 command completed without errors Link means that visual studio was able to link a sample executable to a library (libboost_thread-vcXXX-mt[-gd]-1_XX.lib) generated Execute means that the linked program executed without errors. The full log is at: https://gist.github.com/teeks99/b59b073cdf08f08d5fd6d170721c92ca Tom
On 11/15/2018 7:37 AM, Tom Kent via Boost wrote:
On Wed, Nov 14, 2018 at 4:50 PM 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.
We're still seeing the same msvc-8.0 errors:
compile-c-c++ bin.v2\libs\log\build\msvc-8.0\release\link-static\threadapi-win32\threading-multi\trivial.obj trivial.cpp .\boost/parameter/aux_/arg_list.hpp(227) : error C2064: term does not evaluate to a function taking 1 arguments .\boost/parameter/aux_/arg_list.hpp(390) : see reference to class template instantiation 'boost::parameter::aux::arg_list<TaggedArg,Next>' being compiled
Please check if mpl has commit ac67f5952e6c849e461d7651ffb4fa0e7f380bb0 on 'master'. This is the commit which fixes the above problem in msvc-8.0. It may not have made it in to the second beta release.
toolset arch compile Link Execute msvc-8.0 32 FAIL X X msvc-8.0 64 FAIL X X msvc-9.0 32 X X X msvc-9.0 64 X X X msvc-10.0 32 X X X msvc-10.0 64 X X X msvc-11.0 32 X X X msvc-11.0 64 X X X msvc-12.0 32 X X X msvc-12.0 64 X X X msvc-14.0 32 X X X msvc-14.0 64 X X X msvc-14.1 32 X X X msvc-14.1 64 X X X
Compile means that the b2 command completed without errors Link means that visual studio was able to link a sample executable to a library (libboost_thread-vcXXX-mt[-gd]-1_XX.lib) generated Execute means that the linked program executed without errors.
The full log is at: https://gist.github.com/teeks99/b59b073cdf08f08d5fd6d170721c92ca
Tom
On 11/14/18 2:50 PM, Marshall Clow via Boost wrote: Marshall, I would like to merge development of the serialization library into the master if there is an opportunity to do so. If not, I'll just wait until after the release. I know you've complained about merging w/o permission. I'm not a git guru but can't you tag the current state and work with that independently of what anyone subsequently merges. Also there's creating a branch for the merge. Also the possibility of keeping the release candidate on your own machine and only pulling what you want to explictly merge. Just food for thought? Robert Ramey
On Thu, Nov 15, 2018 at 11:37 AM Robert Ramey via Boost < boost@lists.boost.org> wrote:
On 11/14/18 2:50 PM, Marshall Clow via Boost wrote:
Marshall,
I would like to merge development of the serialization library into the master if there is an opportunity to do so. If not, I'll just wait until after the release.
After the beta release, sure.
I know you've complained about merging w/o permission. I'm not a git guru but can't you tag the current state and work with that independently of what anyone subsequently merges. Also there's creating a branch for the merge. Also the possibility of keeping the release candidate on your own machine and only pulling what you want to explictly merge. Just food for thought?
Or you can merge to release locally and not push those changes until later. -- Marshall
participants (9)
-
degski -
Edward Diener -
Marshall Clow -
Olaf van der Spek -
Paul A. Bristow -
Peter Dimov -
Robert -
Robert Ramey -
Tom Kent