The second release candidates for the 1.61.0 release are now available at: http://boost.cowic.de/rc/boost_1_61_0_rc2.zip http://boost.cowic.de/rc/boost_1_61_0_rc2.7z http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.gz The SHA256 checksums are as follows: fa1c34862b7ba8674ed6e064a14667a11830c6252f702d9458451834b74f7815 boost_1_61_0_rc2.7z a547bd06c2fd9a71ba1d169d9cf0339da7ebf4753849a8f7d6fdb8feee99b640 boost_1_61_0_rc2.tar.bz2 a77c7cc660ec02704c6884fbb20c552d52d60a18f26573c9cee0788bf00ed7e6 boost_1_61_0_rc2.tar.gz 02d420e6908016d4ac74dfc712eec7d9616a7fc0da78b0a1b5b937536b2e01e8 boost_1_61_0_rc2.zip The changes relative to RC1 are MSVC fixes for signals2 and graph libraries. 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 signed list of checksums is also attached, signed with the following key: https://pgp.mit.edu/pks/lookup?op=get&search=0xDA472E8659753BA4 Key fingerprint C5F0 F367 AA66 616F B839 806E DA47 2E86 5975 3BA4 Thanks! -- The release managers
http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.bz2 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.
Built with MSVC (Visual Studio version 14.0.25123.00 Update 2) using this command line: b2 -j12 build-type=complete The build completed successfully but with warnings (see attached text file). The warnings seem benign with these exceptions: d:\lib\boost_1_61_0\boost\graph\named_function_params.hpp(240) : warning C4172: returning address of local variable or temporary D:\lib\boost_1_61_0\boost/signals/slot.hpp(51): warning C4251: 'boost::signals::detail::slot_base::data': class 'boost::shared_ptr<boost::signals::detail::slot_base::data_t>' needs to have dll-interface to be used by clients of class 'boost::signals::detail::slot_base' Hope this helps
On 07/05/2016 15:59, Vinnie Falco wrote:
http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.bz2 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.
Built with MSVC (Visual Studio version 14.0.25123.00 Update 2) using this command line:
b2 -j12 build-type=complete
Vinnie, thanks for giving this a try!
The build completed successfully but with warnings (see attached text file). The warnings seem benign with these exceptions:
d:\lib\boost_1_61_0\boost\graph\named_function_params.hpp(240) : warning C4172: returning address of local variable or temporary
Yep, sounds scary, but this line appears to be from 2012, so probably not a release blocker. Can anybody looks at this after release?
D:\lib\boost_1_61_0\boost/signals/slot.hpp(51): warning C4251: 'boost::signals::detail::slot_base::data': class 'boost::shared_ptr<boost::signals::detail::slot_base::data_t>' needs to have dll-interface to be used by clients of class 'boost::signals::detail::slot_base'
I'd guess we can pass on this as well, given that Boost.Signals is deprecated. Thanks again, -- Vladimir Prus http://vladimirprus.com
On May 7, 2016, at 7:12 AM, Vladimir Prus <vladimir.prus@gmail.com> wrote:
On 07/05/2016 15:59, Vinnie Falco wrote:
http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.bz2 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.
Built with MSVC (Visual Studio version 14.0.25123.00 Update 2) using this command line:
The build completed successfully but with warnings (see attached text file). The warnings seem benign with these exceptions:
d:\lib\boost_1_61_0\boost\graph\named_function_params.hpp(240) : warning C4172: returning address of local variable or temporary
Yep, sounds scary, but this line appears to be from 2012, so probably not a release blocker. Can anybody looks at this after release?
I’ll take a look, thanks for the report. Noel
On Sat, May 7, 2016 at 6:31 AM, Vladimir Prus <vladimir.prus@gmail.com> wrote:
The second release candidates for the 1.61.0 release are now available at:
http://boost.cowic.de/rc/boost_1_61_0_rc2.zip http://boost.cowic.de/rc/boost_1_61_0_rc2.7z http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.gz
The .zip archive is missing from boost.cowic.de/rc. Tom
On 07/05/2016 16:08, Tom Kent wrote:
On Sat, May 7, 2016 at 6:31 AM, Vladimir Prus <vladimir.prus@gmail.com> wrote:
The second release candidates for the 1.61.0 release are now available at:
http://boost.cowic.de/rc/boost_1_61_0_rc2.zip http://boost.cowic.de/rc/boost_1_61_0_rc2.7z http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.gz
The .zip archive is missing from boost.cowic.de/rc.
Thanks for the catch - I've now definitely uploaded it :-) -- Vladimir Prus http://vladimirprus.com
On Sat, May 7, 2016 at 6:31 AM, Vladimir Prus <vladimir.prus@gmail.com> wrote:
The second release candidates for the 1.61.0 release are now available at:
http://boost.cowic.de/rc/boost_1_61_0_rc2.zip http://boost.cowic.de/rc/boost_1_61_0_rc2.7z http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.gz
The SHA256 checksums are as follows:
fa1c34862b7ba8674ed6e064a14667a11830c6252f702d9458451834b74f7815 boost_1_61_0_rc2.7z a547bd06c2fd9a71ba1d169d9cf0339da7ebf4753849a8f7d6fdb8feee99b640 boost_1_61_0_rc2.tar.bz2 a77c7cc660ec02704c6884fbb20c552d52d60a18f26573c9cee0788bf00ed7e6 boost_1_61_0_rc2.tar.gz 02d420e6908016d4ac74dfc712eec7d9616a7fc0da78b0a1b5b937536b2e01e8 boost_1_61_0_rc2.zip
The changes relative to RC1 are MSVC fixes for signals2 and graph libraries.
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.
Tests look good: 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 Compile means that the b2 command completed without errors Install means that the installers for the respective version were generated 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 build output can be found here. https://gist.github.com/teeks99/a30fcfa23aba7bbff03a8ee3f7fbdc6e#file-boost_... https://gist.github.com/teeks99/8e34ad1357df444f92c99b7836144027#file-boost_... Tom
On Sat, May 7, 2016 at 4:31 AM, Vladimir Prus <vladimir.prus@gmail.com> wrote:
The second release candidates for the 1.61.0 release are now available at:
http://boost.cowic.de/rc/boost_1_61_0_rc2.zip http://boost.cowic.de/rc/boost_1_61_0_rc2.7z http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.gz
The SHA256 checksums are as follows:
fa1c34862b7ba8674ed6e064a14667a11830c6252f702d9458451834b74f7815 boost_1_61_0_rc2.7z a547bd06c2fd9a71ba1d169d9cf0339da7ebf4753849a8f7d6fdb8feee99b640 boost_1_61_0_rc2.tar.bz2 a77c7cc660ec02704c6884fbb20c552d52d60a18f26573c9cee0788bf00ed7e6 boost_1_61_0_rc2.tar.gz 02d420e6908016d4ac74dfc712eec7d9616a7fc0da78b0a1b5b937536b2e01e8 boost_1_61_0_rc2.zip
The changes relative to RC1 are MSVC fixes for signals2 and graph libraries.
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 successfully built the .bz2 release with Apple's clang with C++03/11/14/1z. -- Marshall
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/07/2016 06:31 AM, Vladimir Prus wrote:
The second release candidates for the 1.61.0 release are now available at:
http://boost.cowic.de/rc/boost_1_61_0_rc2.zip http://boost.cowic.de/rc/boost_1_61_0_rc2.7z http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_rc2.tar.gz
The SHA256 checksums are as follows:
fa1c34862b7ba8674ed6e064a14667a11830c6252f702d9458451834b74f7815 boost_1_61_0_rc2.7z a547bd06c2fd9a71ba1d169d9cf0339da7ebf4753849a8f7d6fdb8feee99b640 boost_1_61_0_rc2.tar.bz2 a77c7cc660ec02704c6884fbb20c552d52d60a18f26573c9cee0788bf00ed7e6 boost_1_61_0_rc2.tar.gz 02d420e6908016d4ac74dfc712eec7d9616a7fc0da78b0a1b5b937536b2e01e8 boost_1_61_0_rc2.zip
The changes relative to RC1 are MSVC fixes for signals2 and graph libraries.
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 signed list of checksums is also attached, signed with the following key:
https://pgp.mit.edu/pks/lookup?op=get&search=0xDA472E8659753BA4 Key fingerprint C5F0 F367 AA66 616F B839 806E DA47 2E86 5975 3BA4
Thanks!
-- The release managers
I have verified that the hashes of the downloaded libraries (and the one I built the windows binaries from) match those in the above message. However, I was unable to verify that they were correctly signed, as the attached signature file didn't contain the hashes. Also, once the files are renamed for the release, the hashing script should be re-run so that the correct filenames (without the _rc2) are listed for the file hashes (the actual hashes should be the same as whatever rc* is eventually released). Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJXMTj/AAoJEO5CwwL7YZSoL1oP/0t1a8dWcx7HXzHppOq6OuTu slyNeMXDLYD+sDjD91lrSE2ESdEpdxDf8ljAeniLfvXcyx5p5/EmtaCmdAlCExeo AMcnsWvKbTZdDEQWC7HVj+xUKkuGgqFjXCEu+wthoB/13IcUOd0DEoFMPVyzRxF0 FVLCyJNv4tcP3rpBtw0c5axkE8ODG8y+t6g5EOn7Jjhv6IZ984SpEE9YmuaGZ2i7 xOKXNw/ds/qkTEzjeBtKbpjde2FMgSMS4j+VtrfHEQfDofde0gvzGwSMHkxX9GeT 5+1BcSgfcC5yHpFgu4UjgoU1c3qqHztqWn5gjal5x8O1we99gfahhqXlAZ8GBngL B3BnihoQcikGdudDbUHqsQ1L7cUNR+nuPPfEHQJhoWzksBevjG58HUSTlKkaaDNX Yk3lmMqdyeaHgqgYbhnc+DDM8Xap8mQKZX09R18v8+tQhJMAzlsT6OJ61hoAcS3i jLe1CNP2vB0FnTb1rA6jk30pNzArFaneTgwXzn6sueE5kkcoWVSwow4C8z4SERkQ e2pRDm93Lwn+69YTLnMP1ITvrxSaI8o8spfrZ5bW+ewcRnlQycmttRQ9Td9yMe/E rC3bLoJtN8g9iy7xvfV+dus6JBfvBYfDjY047qKAnpznkHuTkRBDAgvE7k9UfjQU KyZ9Y9nfw/eSwgErFtrb =zfRs -----END PGP SIGNATURE-----
The second release candidates for the 1.61.0 release are now available at:
might be too late for 1.61, but since msvc's update fixed one compiler bug by introducing another, boost.lockfree won't compile with the latest msvc update. the least intrusive change i could come up with is the following: https://github.com/boostorg/lockfree/commit/547f131cb0034ea9d8fe5de33911730c... it doesn't introduce any functional change, but gives users the possibility to force the use of boost::atomic instead of relying on std::atomic by defining the BOOST_LOCKFREE_FORCE_BOOST_ATOMIC macro. is it ok to merge this into master before 1.61 comes out? we could add a release note: -- Due to a bug in VS 2015 Update 2 boost.lockfree might trigger error C2338. The suggested workaround is to define BOOST_LOCKFREE_FORCE_BOOST_ATOMIC. -- cheers, tim
[Tim Blechmann]
we could add a release note: Due to a bug in VS 2015 Update 2 boost.lockfree might trigger error C2338.
This is not a bug. I think I've explained this sufficiently. STL
[Tim Blechmann]
we could add a release note: Due to a bug in VS 2015 Update 2 boost.lockfree might
On Wednesday, 11 May 2016 19:36:42 MSK Stephan T. Lavavej wrote: trigger error C2338.
This is not a bug. I think I've explained this sufficiently.
I think I agree with Tim on this. The code is valid according to the standard, and the compiler rejects it.
On 2016-05-11 18:37, Andrey Semashev wrote:
[Tim Blechmann]
we could add a release note: Due to a bug in VS 2015 Update 2 boost.lockfree might
On Wednesday, 11 May 2016 19:36:42 MSK Stephan T. Lavavej wrote: trigger error C2338.
This is not a bug. I think I've explained this sufficiently.
I think I agree with Tim on this. The code is valid according to the standard, and the compiler rejects it.
But it's not a bug if it is done on purpose.
On Wednesday, 11 May 2016 20:04:16 MSK Bo Persson wrote:
On 2016-05-11 18:37, Andrey Semashev wrote:
On Wednesday, 11 May 2016 19:36:42 MSK Stephan T. Lavavej
wrote:
[Tim Blechmann]
we could add a release note: Due to a bug in VS 2015 Update 2 boost.lockfree might
trigger error C2338.
This is not a bug. I think I've explained this sufficiently.
I think I agree with Tim on this. The code is valid according to the standard, and the compiler rejects it.
But it's not a bug if it is done on purpose.
The behavior contradicts the standard and therefore is a bug. The intention doesn't matter.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
we could add a release note: Due to a bug in VS 2015 Update 2 boost.lockfree might
trigger error C2338.
This is not a bug. I think I've explained this sufficiently.
I think I agree with Tim on this. The code is valid according to the standard, and the compiler rejects it.
But it's not a bug if it is done on purpose.
The behavior contradicts the standard and therefore is a bug. The intention doesn't matter.
* msvc had a bug * boost.lockfree didn't trigger the bug * msvc fixed the bug, rejecting valid code which didn't trigger a bug * from the point of view of boost.lockfree this is a regression - -- it is perfectly fine to introduce one bug (even a regression) on purpose in order to fix another. i can absolutely understand the rationale behind it. however the wording that "This is not a bug" and "If this has already been fixed in 1.61.0, then that's great" is unprofessional: it implies that the behavior is standard-compliant and that the user code (boost.lockfree) contains a bug, while in truth boost.lockfree would have to work around a compiler bug. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXM3dBAAoJEAIkvWiom07DE0EP+wYPfJGwIDUAkn1sT44ZSqCb 6HKRev1I7zpBFmYuP8QDaMb5w22e9tvQeu/NQyxjsc8G+5viRRofyC876CKPCulc q8e8SURZJPDSX4GivTw2Tjgqnaa6XJXVqKSJv1otv/4clWGuIKpTgki1N5IhOwjS eSzZwKV20GAdLbMBjPwncMVL9urkZVN0sAqqF5Fp3VDAUN3m/bbfqDWMh1PRAZfZ 0WB7Rt9gXFaPQm73qCyDSIwB+X2PawBuxDneXmLP3L9oEdPrRxuVHE6AAA/YshtI Ssewh1kut7U6+hxgdI+nUTWC1nWsvAc14g643GBO9Xtgzs3/tSllVtylJnXfFv/U MOp29pVLfzglkMvZvBoraqpH9HiEv1OSP4PfUT+bBdoeazf3/y2Qhec8zXwq/T5v ur+qT7iwncqD4qs2a4uXORfEE7GegTFWbVDRstgqq9zGqGcpdM9ZY/8egkegFcDT K1Cgsa/Jm8vYMQX9Fb7yJb2OyR5/mSE8ZmOhnGwCMEgIo2jukB06vVsVQBTcssCc thPLhp0BErVqytH49IGLC0zGa1dTQ+3ziRwSf74lwQ9r9vL7/fUNAEW/r2RU2/OI IJahMj138ntr7bpU5VkNpFcV1cLOR/C5XtA0MDcIgBkHqZORVh19QuK8Fn8hDIlW 8FALeaj1Qohs6okCTF6Q =3Duz -----END PGP SIGNATURE-----
participants (9)
-
Andrey Semashev -
Belcourt, Kenneth -
Bo Persson -
Marshall Clow -
Stephan T. Lavavej -
Tim Blechmann -
Tom Kent -
Vinnie Falco -
Vladimir Prus