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

Subject: Re: [boost] [release] Boost 1.69.0 Beta 1 Release Candidate 2
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2018-11-16 16:58:37

> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Robert via Boost
> Sent: 16 November 2018 16:33
> To: boost_at_[hidden]
> 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_at_[hidden]
> > wrote:
> >
> >> On Thu, 15 Nov 2018 at 20:48, Marshall Clow <mclow.lists_at_[hidden]> wrote:
> >>
> >>>
> >>>
> >>> 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"
> >>>>
> >>>> 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