Re: [boost] 1.57.0 beta 1 is now available

On 10/24/2014 10:05 PM, Marshall Clow wrote:

On Oct 24, 2014, at 7:07 AM, Vladimir Prus wrote:

...

On 10/21/2014 02:14 AM, Marshall Clow wrote:

...

Boost release 1.57.0 beta 1 is now available from SourceForge

See http://sourceforge.net/projects/boost/files/boost-binaries/1.57.0.beta.1/

This release contains no new libraries.

For details of what's in the release, see http://www.boost.org/users/history/version_1_57_0.html. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files.

Please download the beta, give it a try, and report any problems you encounter.

Two questions:

- Do we need https://github.com/boostorg/build/commit/252b5aa019dd1b502892e406dc1cd91d128... to be merged to master? It was meant to see some hangs on Solaris, IIUC.

Do we have any way to test this?

Not me, thats why I'm asking.

...

- I'm about to merge couple other Boost.Build changes to master, mostly in Python port. I'm assuming that's as safe as it could be, but let me know if you think otherwise.

If you think they’re safe (and they’ve been in use on develop for a while), then that’s OK.

I've merged Boost.Build develop, as of 2f6ee88755153d0a9a669ae9e3a798212c42e218, to master. These commits remain not merged: Aaron Boman (1): Preserve order of properties in PropertySet. Jurko (5): Fix a dependecy --> dependency comment typo. Fix error message typo - same named targets with different properties. Fix dependendency --> dependency comment typo. Fix comment typos. Return valid exit code from Windows batch scripts. Noel Belcourt (1): Block SIGCHLD during select. kjedruczyk (1): Fixed null ptr dereference in executable_path on solaris when getexecname fails. For those, I either cannot judge their safety, or don't find them important enough to warrant cherry-picking. I'll be traveling until 28th, with not much of free time, so feel free to cherry-pick any of these, if necessary. - Volodya