March 2016 - Boost - lists.boost.org

Boost 1.61.0 Beta 1
by Vladimir Prus 06 Apr '16

06 Apr '16

The first beta packages for 1.61.0 beta 1 are now available: http://boost.cowic.de/rc/boost_1_61_0_b1.zip http://boost.cowic.de/rc/boost_1_61_0_b1.7z http://boost.cowic.de/rc/boost_1_61_0_b1.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_b1.tar.gz There are no changes compared to RC2, expect for different names of the archives and different name of the top-level directory in the archives. The SHA256 checksums are as follows: 3f8888099ee6f62b412a13be916dead2bacbdd6d69e5afd5b6fea4bb738e5df4 boost_1_61_0_b1.7z 866941f0038b27fcc69ced1490b2dc5fa8d20f505d66b939a92a68ef194d1a6c boost_1_61_0_b1.tar.bz2 0b92c5fb5b91641409b9675b2fd11d3b3fa5f71dd986d3b5fb03da201bf55474 boost_1_61_0_b1.tar.gz 9dffe5ee7f5f7bf7695f5738c686e44bd266933e3ca68732b0de5520c3c82615 boost_1_61_0_b1.zip Signed list of checksums should be posted within 24 hours. 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. It was discovered that the .zip and .7z archives actually have LF line endings, at least in some places. Fixing this is not quite trivial, as Travis uses ancient version of Ubuntu and Git, and is not deemed critical, as most Windows editors handle LF just fine. We might do something for the final release, or might not. Thanks! -- The release managers

6 14

[build] How to use with clang on windows?
by John Maddock 03 Apr '16

03 Apr '16

What's the correct way to configure clang on windows with current Boost.Build? If I use: using clang-win : 3.7 : "C:/Progra~2/MICROS~4.0/VC/Clang 3.7/bin/x86/clang.exe" : <cxxflags>-std=c++11 <compatibility>vc14 ; to configure the clang that ships with VC14 I see: compile-c-c++ ..\..\..\bin.v2\libs\smart_ptr\test\shared_ptr_basic_test.test\clang-vc14-win-3.7\debug\shared_ptr_basic_test.obj clang.exe: error: no such file or directory: '/Od' clang.exe: error: no such file or directory: '/Ob0' clang.exe: error: no such file or directory: '/W3' clang.exe: error: no such file or directory: '/GR' clang.exe: error: no such file or directory: '/MDd' clang.exe: error: no such file or directory: '/Zc:forScope' clang.exe: error: no such file or directory: '/Zc:wchar_t' clang.exe: error: no such file or directory: '/wd4675' clang.exe: error: no such file or directory: '/EHs' Same errors with the llvm clang-3.9. On the other hand if I initialize with: using clang : : "C:/Progra~2/LLVM/bin/clang.exe" : <cxxflags>-std=c++14 <compatibility>vc14 <cxxflags>-fms-compatibility-version=19.00.22609 ; Then this sort of works for llvm clang, but not the msvc one (can't find c2.exe), but the compiler is identified as "clang-linux" and I see: LINK : warning LNK4044: unrecognized option '/-start-group'; ignored LINK : warning LNK4044: unrecognized option '/Bstatic'; ignored LINK : warning LNK4044: unrecognized option '/Bdynamic'; ignored LINK : warning LNK4044: unrecognized option '/-end-group'; ignored Plus some linker errors such as: yield_k_test.obj : error LNK2019: unresolved external symbol __mm_pause referenced in function "void __cdecl boost::detail::yield(unsigned int)" (?yield@detail@boost@@YAXI@Z) Ideas? Thanks, John.

7 29

Boost 1.61.0 open for fixes
by Vladimir Prus 02 Apr '16

02 Apr '16

The master branch is now open for bugfixes for 1.61.0. Please make sure that develop tests are healthy prior to merging. We're two weeks late relative to the plan, so further dates were also moved by two weeks in the calendar. -- The release managers

2 1

[Trac][convert] Associate Vladimir as author of Boost.Convert
by Vicente J. Botet Escriba 01 Apr '16

01 Apr '16

Hi, I requested sometime ago to add convert to the Trac system. It was done, but it was associated to me as maintainer. Please, could someone assign it to Vladimir Batov Vladimir, I guess you need to give your use in name. Best, Vicente Convert <http://www.boost.org/doc/libs/1_60_0/libs/convert/> An extendible and configurable type-conversion framework. Author(s) Vladimir Batov First Release 1.59.0

4 5

Coroutine2 examples - Cannot link properly.
by Carlos Ferreira 01 Apr '16

01 Apr '16

Hello to all. I'm having trouble in compiling the coroutine2 examples. For the fibonacci example, the following linking error occurs: /usr/include/boost/coroutine2/detail/pull_control_block.ipp:62: undefined reference to `boost::context::execution_context::current()' Now, I know that I have to link against boost context, something that I'm already doing, but for some reason, it is not enough. Can anyone help me with this? Thank you. -- Carlos Miguel Ferreira Researcher at Telecommunications Institute Aveiro - Portugal Work E-mail - cmf(a)av.it.pt Skype & GTalk -> carlosmf.pt(a)gmail.com LinkedIn -> http://www.linkedin.com/in/carlosmferreira

3 14

[boost 1.61] authorization to merge to master
by Raffi Enficiaud 31 Mar '16

31 Mar '16

Dear Boost, I would like to merge a boost.test bugfix to master. Those changes are running on develop for a week. I haven't done my PR for the website change log update because of that (would change the content of the PR). According to the schedule, boost 1.61 is open for bugfixes since 10 days now, but as I understood, we are still waiting for post RC2 go. - do I still have time for the website PR? - would the opening 1.61 for bugfixes be announced on the ML? - Am I allowed to merge those changes, so that I can reopen develop for post 1.61 developments? Thanks, Raffi Enficiaud

2 2

[boost 1.61 - [thread] Request for permission to merge
by Vicente J. Botet Escriba 31 Mar '16

31 Mar '16

Hi, I would like to merge once it is announced that the release branch is open for fixes a minor fix https://svn.boost.org/trac/boost/ticket/11562 - (condition_variable_any::wait_until + recursive_mutex + steady_clock) timer expires after computer time is set forward on Ubuntu 64-bit add missing template parameter in wait_until. https://github.com/boostorg/thread/commit/9db70b803d8f45632cd92cd61ab019c1f… and the rollback of something that resulted in a regression https://svn.boost.org/trac/boost/ticket/12049 - Assertion failure from detached threads during shutdown rollback BOOST_THREAD_PATCH. https://github.com/boostorg/thread/commit/47357de276fe4fc01469f34c1dbf8b26f… Best, Vicente

1 1

Re: [boost] [filesystem] Horrible documentation
by Tatsuyuki Ishi 31 Mar '16

31 Mar '16

> From: Edward Diener <eldiener(a)tropicsoft.com> > Date: Wed, 30 Mar 2016 00:06:00 -0400 > Subject: Re: [boost] [filesystem] Horrible documentation > > What sort of documentation unification with other libraries do you mean ? By saying unification, I'm talking about the green-background header. It's in most documentation and also on the homepage. > Can you not increase the font size, if it is too small for you to read, in your preferred browser since the doc is HTML ? The layout is quite problematic. Not only the font, text breaks border, and the page is too tall(long). I noticed it's created with FrontPage 2002. Come on, this is 2016.

3 2

[release] Download data
by Daniel James 31 Mar '16

31 Mar '16

Hi, Currently the download details for a release are included in the quickbook source file for the release notes, which is a bit wonky, and makes it tricky to add extra data, so I'm thinking about storing it separately. This should make it easier to add things like hash signatures and links to third party downloads, such as the windows binaries. So I'm thinking about how to make it easy for people to add the details of their downloads. Could possibly create an extra file for each release, and then people can add data using pull requests, much as we've been using pull requests on the quickbook files, which seems to work fairly well. Another possibility is that we could pull in the details from the server's API, although I don't really fancy having to support multiple data sources with different APIs. Any other ideas? Also, is there any way in which you'd like me to make this kinds of information available for your scripts, packaging etc. Here's a rough version of how the internal data might be stored in a JSON file (other file formats are possible): { 'version': '1.61.0', 'status': 'beta', 'release-notes': '/feed/history/boost_1_61_0.qbk', 'documentation': '/doc/libs/1_61_0/', 'downloads': [ { 'url': 'http://..../boost_1_61_0_beta1.tar.bz2', 'hash': '484c635.....' }, { 'url': 'http://..../boost_1_61_0_beta1.7z', 'hash': 'f93de8.....' }, // ... ], 'third-party': [ { 'url': 'http://...', 'title': 'Windows binaries', 'whatever_else': '' } ] }

1 0

[filesystem] Horrible documentation
by Tatsuyuki Ishi 30 Mar '16

30 Mar '16

Sorry for complaining. Is there any plan to use any documentation tool to regenerate this? It's not unified with other libraries, and too horrible due to the small font size. I really can't read that.

2 1