[1.56.0] Release Candidate 3 available
We've created a third release candidate to fix a one more issue with Boost.Range. The files for 1.56.0 RC3 are available at: http://boost.cowic.de/rc/ 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 files (and associated md5s) are: MD5 (./boost_1_56_0_rc3.7z) = b7a72a6a6f487fa445333b4e115c6171 MD5 (./boost_1_56_0_rc3.tar.bz2) = a744cf167b05d72335f27c88115f211d MD5 (./boost_1_56_0_rc3.tar.gz) = 8c54705c424513fa2be0042696a3a162 MD5 (./boost_1_56_0_rc3.zip) = fc16da21d641e03715a4144cb093964e Thanks! -- The release managers
On 5 August 2014 22:19, Marshall Clow
It's probably too late to fix now, but the directories have permission 700, they probably should be 755, so that they're readable by everyone. FWIW this is the command I used to do this for the website: find boost_1_56_0 -type d | xargs chmod 755 Not the most difficult command, but it might help someone. The documentation is on the website at: http://www.boost.org/doc/libs/1_56_0/ I'll fix the libraries that are incorrectly labeled 'unreleased' soon. Just pretend it's because they're not quite released yet, and not because I'm forgetful.
On Tuesday 05 August 2014 23:37:12 Daniel James wrote:
The documentation is on the website at:
Why Boost.Atomic docs start with Chapter 5 on the front page? http://www.boost.org/doc/libs/1_56_0/doc/html/atomic.html It's not something new in 1.56, I can see it in 1.55 too. I can see it in Boost.Align as well. It's definitely not a blocker for 1.56, but I'd like to fix it if possible.
On 6/08/2014 14:07, Andrey Semashev wrote:
Click on the Up link (http://www.boost.org/doc/libs/1_56_0/doc/html/libraries.html). That's why it's Chapter 5. (I don't know why the libraries are listed in that order or why it appears to only have a subset of libraries, but presumably those are artifacts of the way the docs are built.)
On Wednesday 06 August 2014 14:47:10 Gavin Lambert wrote:
Thanks for the pointer. It looks like all docs that are built in boost_root/doc are numbered this way, and I can't change it in the library docs. Since that library list is not exhaustive (and probably not visible on the website?), is it really needed?
Built successfully on Linux - gcc-4.9/clang-3.6 with clang a lot of the same warnings: ./boost/mpl/if.hpp:131:1: warning: empty macro arguments are a C99 feature [-Wc99-extensions] ./boost/preprocessor/variadic/elem.hpp:28:42: warning: variadic macros are a C99 feature [-Wvariadic-macros] clang: warning: optimization flag '-finline-functions' is not supported clang: warning: argument unused during compilation: '-finline-functions' Kris -- View this message in context: http://boost.2283326.n4.nabble.com/1-56-0-Release-Candidate-3-available-tp46... Sent from the Boost - Dev mailing list archive at Nabble.com.
On Tue, Aug 5, 2014 at 9:19 PM, Marshall Clow
Looks good on windows: toolset arch compile install Link Execute msvc-8.0 32 X X X X msvc-8.0 64 X X X X msvc-9.0 32 X X X X msvc-9.0 64 X X X X msvc-10.0 32 X X X X msvc-10.0 64 X X X X msvc-11.0 32 X X X X msvc-11.0 64 X X X X msvc-12.0 32 X X X X msvc-12.0 64 X 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. Tom
Thanks to everyone who reported their RC results. The RC reporting coverage has been much better than for past releases, and that is very helpful indeed! --Beman
participants (7)
-
Andrey Semashev -
Beman Dawes -
Daniel James -
Gavin Lambert -
Kris -
Marshall Clow -
Tom Kent