Sorry, I missed your earlier report about TypeIndex. I’ll fix that for the next version. — Marshall On Wed, Jul 9, 2014 at 2:46 AM, Andrey Semashev wrote:

On Tuesday 08 July 2014 22:48:50 Marshall Clow wrote:

...

Release candidate files for 1.56.0 beta 1 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.

This helps ensure the candidates build OK before we push them out to SourceForge.

The files (and associated md5s) are: MD5 (boost-1_56_0b1_rc1.7z) = a23e0b5f503c82970c9754dbc8324256 MD5 (boost-1_56_0b1_rc1.tar.bz2) = c6c8486dde4375896f302bdfe1fd3d2f MD5 (boost-1_56_0b1_rc1.tar.gz) = 1042e97a9f354b7187326fa1f9eb313e MD5 (boost-1_56_0b1_rc1.zip) = 984a70feac785d908d8f75ea9d8d2158

Since this is the first post-git release, we are expecting some teething pains with this release. Please test extensively.

TypeIndex library is still missing.

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Hi Rene, Ah, beta1 RC archive doesn't contain your yesterday's commit. I copy new test/build.jam from github, and then it should work fine. I wish that fixed in next version. Kohei Takahashi (2014/07/11 12:01), Rene Rivera wrote:

I'll look at that ASAP. But since I'm on vacation it might take a few days. On Jul 10, 2014 8:34 PM, "Kohei Takahashi" wrote:

...

Hi,

(2014/07/09 14:48), Marshall Clow wrote:

...

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've confirmed that build succeeded under Fedora20 x86_64 with system provided GCC, but then I've got following error under status directory.

$ cd status $ ../b2 ((snip)) error: Unable to find file or target named error: '/home/flast/boost-1_56_0b1/libs/predef/include/boost/predef.h' error: referred to from project at error: '../libs/predef/test'

Thanks, Kohei Takahashi

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

-----Original Message----- From: Rene Rivera Sender: "Boost" Date: Fri, 11 Jul 2014 08:10:15 To: boost@lists.boost.org Reply-To: boost@lists.boost.org Subject: Re: [boost] 1.56.0 beta 1 release candidates available for testing On Fri, Jul 11, 2014 at 1:54 AM, Kohei Takahashi wrote:

Hi Rene,

Ah, beta1 RC archive doesn't contain your yesterday's commit. I copy new test/build.jam from github, and then it should work fine.

I wish that fixed in next version.

Oh good. I was hoping that change fixed it. But had not gotten to testing the use case from the "status" directory. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

On 12 Jul 2014 at 10:14, Vicente J. Botet Escriba wrote:

...

Since this is the first post-git release, we are expecting some teething pains with this release. Please test extensively.

please could I merge these two commits

Added inline for when_all() and when_any(). https://github.com/boostorg/thread/commit/08c4599fb684d1f1d078b1811f24243644... fix wait_pull_front in case the queue is closed while empty. https://github.com/boostorg/thread/commit/f263c6014e4e5c66fb6aa1a6aa8d67d2d1...

These were committed 1 week ago and there is no visible regression.

I'd also like to merge https://github.com/boostorg/thread/pull/20 into v1.56 release. It fixes a poor 64 bit timers contribution with a solution that actually works as expected on all platforms. It also passes all tests, though I'll admit I haven't actually run test code past the 41 day timer limit the new support eliminates. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/