[release] Boost 1.67.0 Beta 1 Release Candidate 2
The second release candidates for the 1.67.0 beta release are now available at: <https://dl.bintray.com/boostorg/beta/1.67.0.beta.1/source/> The release notes can be previewed at: <http://www.boost.org/users/history/in_progress.html> The documentation is available at: <http://www.boost.org/doc/libs/1_67_0_beta1/> The SHA256 checksums are as follows: 154cf490da858fd9c2307bb904b07a42cbe8355ecf99d5477f0d843c6d03cdda boost_1_67_0_b1_rc2.7z 0d854b208fefaeb5837d6c417f505b189275e32d017f6226001fb165a5ac51ed boost_1_67_0_b1_rc2.tar.bz2 6eb3f9ca8db355765f41361e1e26976228f0c2dff400aade8a5e97aec6aa59f4 boost_1_67_0_b1_rc2.tar.gz 678a6459f2517932536ec97297be1de46ea073f2e2ee17ec8397b80aa0953f49 boost_1_67_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.
On Thu, Mar 15, 2018 at 3:01 PM, Daniel James via Boost <boost@lists.boost.org> wrote:
The second release candidates for the 1.67.0 beta release are now available at:
The Boost C++ Libraries were successfully built! This doesn't look that nice though: C:\VC\boost>b2 libs\python\Jamfile:49: Unescaped special character in argument [*\/:."'] C:/VC/boost/libs/predef/check/../tools/check\predef.jam:46: Unescaped special character in argument $(language)::$(expression) -- Olaf
On 15.03.2018 15:24, Olaf van der Spek via Boost wrote:
On Thu, Mar 15, 2018 at 3:01 PM, Daniel James via Boost <boost@lists.boost.org> wrote:
The second release candidates for the 1.67.0 beta release are now available at: The Boost C++ Libraries were successfully built!
This doesn't look that nice though:
C:\VC\boost>b2 libs\python\Jamfile:49: Unescaped special character in argument [*\/:."']
I had cloned that line from https://github.com/boostorg/boost/blob/master/boostcpp.jam, but I see that has changed since then. I have just pushed https://github.com/boostorg/python/commit/d515eb82c8a1e007651b1e7d75a3141fdc..., so please let me know if you want to incorporate that commit into master for the release. Stefan -- ...ich hab' noch einen Koffer in Berlin...
On 15 March 2018 at 19:31, Stefan Seefeld via Boost <boost@lists.boost.org> wrote:
On 15.03.2018 15:24, Olaf van der Spek via Boost wrote:
On Thu, Mar 15, 2018 at 3:01 PM, Daniel James via Boost <boost@lists.boost.org> wrote:
The second release candidates for the 1.67.0 beta release are now available at: The Boost C++ Libraries were successfully built!
This doesn't look that nice though:
C:\VC\boost>b2 libs\python\Jamfile:49: Unescaped special character in argument [*\/:."']
I had cloned that line from https://github.com/boostorg/boost/blob/master/boostcpp.jam, but I see that has changed since then. I have just pushed https://github.com/boostorg/python/commit/d515eb82c8a1e007651b1e7d75a3141fdc..., so please let me know if you want to incorporate that commit into master for the release.
Those warnings are fairly new, and were added to warn about future incompatibilities. I'd prefer to leave fixing them until after the beta release. Although, IMO the best thing would be to disable the warnings in this release, as there hasn't been enough time to deal with them.
On 15.03.2018 15:45, Daniel James wrote:
On 15 March 2018 at 19:31, Stefan Seefeld via Boost <boost@lists.boost.org> wrote:
On Thu, Mar 15, 2018 at 3:01 PM, Daniel James via Boost <boost@lists.boost.org> wrote:
The second release candidates for the 1.67.0 beta release are now available at: The Boost C++ Libraries were successfully built!
This doesn't look that nice though:
C:\VC\boost>b2 libs\python\Jamfile:49: Unescaped special character in argument [*\/:."'] I had cloned that line from https://github.com/boostorg/boost/blob/master/boostcpp.jam, but I see
On 15.03.2018 15:24, Olaf van der Spek via Boost wrote: that has changed since then. I have just pushed https://github.com/boostorg/python/commit/d515eb82c8a1e007651b1e7d75a3141fdc..., so please let me know if you want to incorporate that commit into master for the release. Those warnings are fairly new, and were added to warn about future incompatibilities. I'd prefer to leave fixing them until after the beta release. Although, IMO the best thing would be to disable the warnings in this release, as there hasn't been enough time to deal with them.
OK, fine. I'll cherry-pick the commit once master is open again for fixes. Stefan -- ...ich hab' noch einen Koffer in Berlin...
On Thu, Mar 15, 2018 at 10:01 AM, Daniel James via Boost < boost@lists.boost.org> wrote:
The second release candidates for the 1.67.0 beta release are now available at:
<https://dl.bintray.com/boostorg/beta/1.67.0.beta.1/source/>
The release notes can be previewed at:
<http://www.boost.org/users/history/in_progress.html>
The documentation is available at:
<http://www.boost.org/doc/libs/1_67_0_beta1/>
The SHA256 checksums are as follows:
154cf490da858fd9c2307bb904b07a42cbe8355ecf99d5477f0d843c6d03cdda boost_1_67_0_b1_rc2.7z 0d854b208fefaeb5837d6c417f505b189275e32d017f6226001fb165a5ac51ed boost_1_67_0_b1_rc2.tar.bz2 6eb3f9ca8db355765f41361e1e26976228f0c2dff400aade8a5e97aec6aa59f4 boost_1_67_0_b1_rc2.tar.gz 678a6459f2517932536ec97297be1de46ea073f2e2ee17ec8397b80aa0953f49 boost_1_67_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.
Windows Server with MSVC 10.0 through 14.1 installed; 03/15/2018 10:05 AM 155,243,735 boost_1_67_0_b1_rc2.zip c:\Temp\boost_1_67_0>.\b2.exe toolset=msvc-10.0,msvc-11.0,msvc-12.0,msvc-14.0,msvc-14.1 variant=debug,release link=shared,static address-model=32,64 threading=multi,single -q ...found 159899 targets... ...updating 23106 targets... msvc.link.dll bin.v2\libs\program_options\build\msvc-10.0\debug\threading-multi\boost_program_options-vc100-mt-gd-x32-1_67.dll Creating library bin.v2\libs\program_options\build\msvc-10.0\debug\threading-multi\boost_program_options-vc100-mt-gd-x32-1_67.lib and object bin.v2\libs\program_options\build\msvc-10.0\debug\threading-multi\boost_program_options-vc100-mt-gd-x32-1_67.exp msvc.manifest.dll bin.v2\libs\program_options\build\msvc-10.0\debug\threading-multi\boost_program_options-vc100-mt-gd-x32-1_67.dll common.copy stage\lib\boost_program_options-vc100-mt-gd-x32-1_67.dll bin.v2\libs\program_options\build\msvc-10.0\debug\threading-multi\boost_program_options-vc100-mt-gd-x32-1_67.dll 1 file(s) copied. common.copy stage\lib\boost_program_options-vc100-mt-gd-x32-1_67.lib bin.v2\libs\program_options\build\msvc-10.0\debug\threading-multi\boost_program_options-vc100-mt-gd-x32-1_67.lib 1 file(s) copied. compile-c-c++ bin.v2\libs\python\build\msvc-10.0\debug\threading-multi\list.obj list.cpp c:\python36\include\pyport.h(6) : fatal error C1083: Cannot open include file: 'inttypes.h': No such file or directory call "bin.v2\standalone\msvc\msvc-10.0\msvc-setup.bat" x86 >nul cl /Zm800 -nologo @"bin.v2\libs\python\build\msvc-10.0\debug\threading-multi\list.obj.rsp" ...failed compile-c-c++ bin.v2\libs\python\build\msvc-10.0\debug\threading-multi\list.obj... ...failed updating 1 target... ...updated 5 targets... inttypes.h is not available on MSVC 10.0 (2010) or earlier; one usually requires the use of the "msinttypes" package in this case... - Jim
On 15 March 2018 at 19:27, James E. King, III <jking@apache.org> wrote:
c:\python36\include\pyport.h(6) : fatal error C1083: Cannot open include file: 'inttypes.h': No such file or directory
[snip]
inttypes.h is not available on MSVC 10.0 (2010) or earlier; one usually requires the use of the "msinttypes" package in this case...
That's an error in a python header, so it doesn't seem like something we can do anything about. They use Visual C++ 14.0 for building python 3.6.
On Thu, Mar 15, 2018 at 9:01 AM, Daniel James via Boost < boost@lists.boost.org> wrote:
The second release candidates for the 1.67.0 beta release are now available at:
<https://dl.bintray.com/boostorg/beta/1.67.0.beta.1/source/>
The release notes can be previewed at:
<http://www.boost.org/users/history/in_progress.html>
The documentation is available at:
<http://www.boost.org/doc/libs/1_67_0_beta1/>
The SHA256 checksums are as follows:
154cf490da858fd9c2307bb904b07a42cbe8355ecf99d5477f0d843c6d03cdda boost_1_67_0_b1_rc2.7z 0d854b208fefaeb5837d6c417f505b189275e32d017f6226001fb165a5ac51ed boost_1_67_0_b1_rc2.tar.bz2 6eb3f9ca8db355765f41361e1e26976228f0c2dff400aade8a5e97aec6aa59f4 boost_1_67_0_b1_rc2.tar.gz 678a6459f2517932536ec97297be1de46ea073f2e2ee17ec8397b80aa0953f49 boost_1_67_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.
Windows builds look good. Full (clean!) build log here: https://gist.github.com/teeks99/23bff88adbef0b64d931a0c11823a0a0 toolset arch compile Link Execute msvc-8.0 32 X X X msvc-8.0 64 X 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. Tom
Hello Daniel and all, On Thu, Mar 15, 2018 at 7:01 AM, Daniel James via Boost <boost@lists.boost.org> wrote:
The second release candidates for the 1.67.0 beta release are now available at:
<https://dl.bintray.com/boostorg/beta/1.67.0.beta.1/source/>
I downloaded and built the .7z file. Libraries got built using G++ 6.4.0 on Cygwin, nothing to report (attached entire ./b2 output just for reference). I also built and ran all Boost.Contract tests and examples, no issue.
The release notes can be previewed at:
Boost.Contract part looks good.
The documentation is available at:
Boost.Contract docs look good. Thank you. --Lorenzo
participants (6)
-
Daniel James -
James E. King, III -
Lorenzo Caminiti -
Olaf van der Spek -
Stefan Seefeld -
Tom Kent