Re: [Boost-users] [boost] [release] Boost 1.69.0 Beta 1 Release Candidate 2

Subject: Re: [Boost-users] [boost] [release] Boost 1.69.0 Beta 1 Release Candidate 2
From: Marshall Clow (mclow.lists_at_[hidden])
Date: 2018-11-15 18:50:08

On Wed, Nov 14, 2018 at 11:12 PM degski <degski_at_[hidden]> wrote:

> On Thu, 15 Nov 2018 at 00:50, Marshall Clow via Boost <
> boost_at_[hidden]> 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