- Boost - lists.preview.boost.org

[release] Boost 1.69.0 Beta 1 Release Candidate 3
by Marshall Clow 17 Nov '18

17 Nov '18

[ Ok, I've rebuilt the RC - and it contains only the changes to function and MPL ] The release candidates for the third 1.69.0 beta release are now available at: <https://dl.bintray.com/boostorg/beta/1.69.0.beta1.rc3/source/> The release notes are not yet final. The SHA256 checksums are as follows: ee0ecd7d31f58474c1e0210089c9e66bd878d4d1e7436ac511e359aa4a9d3e86 ./boost_1_69_0_b1_rc3.7z 3e25c46f2171799caabbeb419ba7859fffb62208f3a1c80798713377ab07af0e ./boost_1_69_0_b1_rc3.tar.bz2 … [View More]

1 1

[spirit] Request to update the master branch with minor doc changes
by Nikita Kniazev 16 Nov '18

16 Nov '18

Do I have a chance to cherry-pick minor doc changes into the upcoming release? I forgot to update version numbers in docs https://github.com/boostorg/spirit/commit/b4f5833cc69f510d3842ba226d8878bb4…

2 1

[build] targeting different versions of libstdc++
by James E. King III 16 Nov '18

16 Nov '18

If I make a system with libstdc++6-dev, libstdc++7-dev, and libstdc++8-dev on it, is there a way to tell clang to use one over the other? By default it will use the latest one. I know that for linking one can use the clang flag "--gcc-toolchain=/usr/lib/gcc/x86_64-linux-gnu/7" to get the link to point at it, but I'm not sure if this also handles the header paths or not. If this option works for both header inclusion and for linking, would I need to specify it as <cxxflags> and also as <linkflags>? Thanks, Jim

2 1

[bjam] [build] Documentation for 1.69
by Cromwell Enage 16 Nov '18

16 Nov '18

Hi, everyone! Will the documentation for Boost.BJam and Boost.Build be included in the release of Boost 1.69? Cromwell D. Enage

5 7

Announcing LEAF, a new error handling library suitable for low latency applications
by Emil Dotchevski 15 Nov '18

15 Nov '18

LEAF (Low-latency Error Augmentation Framework) is a new error handling library which could possibly become the successor of Boost Exception, though LEAF can be used without exceptions too. Official documentation: https://zajo.github.io/leaf/ Features: - No dynamic memory allocations. - Associate objects of arbitrary types with any failure -- when it is initially reported or at a later time. - Compatible with std::error_code, errno and any other error handling API. - Use with or without … [View More]

4 9

Re: [boost] [Boost-users] [release] Boost 1.69.0 Beta 1 Release Candidate 1
by Marshall Clow 14 Nov '18

14 Nov '18

On Mon, Nov 12, 2018 at 4:30 PM Tom Kent via Boost-users < boost-users(a)lists.boost.org> wrote: > > On Mon, Nov 12, 2018 at 9:36 AM Marshall Clow via Boost-users < > boost-users(a)lists.boost.org> wrote: > >> The release candidates for the first 1.69.0 beta release are now >> available at: >> >> <https://dl.bintray.com/boostorg/beta/1.69.0.beta.1.rc1/source/> >> > As always, the release managers would appreciate it if you download … [View More]>> the candidate of your choice and give building it a try. Please report >> both success and failure, and anything else that is noteworthy. >> > > toolset arch compile Link Execute > msvc-8.0 32 FAIL X X > msvc-8.0 64 FAIL 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 FAIL X X > msvc-14.0 64 FAIL X X > msvc-14.1 32 X X X > msvc-14.1 64 X X X > > Compile means that the b2 command completed without errors > 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. > > Full build logs can be found here: > https://gist.github.com/teeks99/526cf2598d1697557e45e590ce9517be > > Lots of errors with msvc-8.0: > > compile-c-c++ > bin.v2\libs\log\build\msvc-8.0\release\link-static\threadapi-win32\threading-multi\trivial.obj > trivial.cpp > .\boost/parameter/aux_/arg_list.hpp(227) : error C2064: term does not > evaluate to a function taking 1 arguments > .\boost/parameter/aux_/arg_list.hpp(390) : see reference to class > template instantiation 'boost::parameter::aux::arg_list<TaggedArg,Next>' > being compiled > > If there is an easy way to fix arg_list.hpp that would be nice, but if > this is the time to stop build 8.0, that's fine too. > > Also numerous errors for many (all dlls?) of the libraries with msvc-14.0. > They all look something like this: > > > msvc.link.dll > bin.v2\libs\atomic\build\msvc-14.0\release\threading-multi\boost_atomic-vc140-mt-x32-1_69.dll > Creating library > bin.v2\libs\atomic\build\msvc-14.0\release\threading-multi\boost_atomic-vc140-mt-x32-1_69.lib > and object > bin.v2\libs\atomic\build\msvc-14.0\release\threading-multi\boost_atomic-vc140-mt-x32-1_69.exp > msvc.link.dll > bin.v2\libs\system\build\msvc-14.0\release\threading-multi\boost_system-vc140-mt-x32-1_69.dll > Creating library > bin.v2\libs\system\build\msvc-14.0\release\threading-multi\boost_system-vc140-mt-x32-1_69.lib > and object > bin.v2\libs\system\build\msvc-14.0\release\threading-multi\boost_system-vc140-mt-x32-1_69.exp > msvc.link.dll > bin.v2\libs\container\build\msvc-14.0\release\threading-multi\boost_container-vc140-mt-x32-1_69.dll > Creating library > bin.v2\libs\container\build\msvc-14.0\release\threading-multi\boost_container-vc140-mt-x32-1_69.lib > and object > bin.v2\libs\container\build\msvc-14.0\release\threading-multi\boost_container-vc140-mt-x32-1_69.exp > msvc.manifest.dll > bin.v2\libs\atomic\build\msvc-14.0\release\threading-multi\boost_atomic-vc140-mt-x32-1_69.dll > 'mt' is not recognized as an internal or external command, > operable program or batch file. > > if exist > "bin.v2\libs\atomic\build\msvc-14.0\release\threading-multi\boost_atomic-vc140-mt-x32-1_69.dll.manifest" > ( > call "bin.v2\standalone\msvc\msvc-14.0\msvc-setup.bat" x86 >nul > mt -nologo -manifest > "bin.v2\libs\atomic\build\msvc-14.0\release\threading-multi\boost_atomic-vc140-mt-x32-1_69.dll.manifest" > "-outputresource:bin.v2\libs\atomic\build\msvc-14.0\release\threading-multi\boost_atomic-vc140-mt-x32-1_69.dll;2" > ) > > ...failed msvc.manifest.dll > bin.v2\libs\atomic\build\msvc-14.0\release\threading-multi\boost_atomic-vc140-mt-x32-1_69.dll > bin.v2\libs\atomic\build\msvc-14.0\release\threading-multi\boost_atomic-vc140-mt-x32-1_69.lib... > ...removing > bin.v2\libs\atomic\build\msvc-14.0\release\threading-multi\boost_atomic-vc140-mt-x32-1_69.dll > ...removing > bin.v2\libs\atomic\build\msvc-14.0\release\threading-multi\boost_atomic-vc140-mt-x32-1_69.lib > > I'm on the fence if we should continue supporting 8.0, so if that doesn't > get fixed then no big deal. However the issue with (the build tool?) for > 14.0 seems like a showstopper for this RC. > > Do we have any idea why MSVC 14 is failing? -- Marshall (who has been distracted by WG21 stuff) [View Less]

4 4

What part of "The master branch is closed except by explicit permission" is confusing?
by Marshall Clow 14 Nov '18

14 Nov '18

That means "DO NOT COMMIT TO THE MASTER BRANCH" FULL STOP. I just turned on the auto-updating for the release, expecting two changes: * one from MPL * one from Function. Instead, I got updated from: * Update mpl from master * Update function from master * Update atomic from master * Update log from master * Update convert from master * Update iostreams from master You're making the release process harder. -- Marshall

3 2

Re: [boost] [Boost-users] [release] Boost 1.69.0 Beta 1 Release Candidate 1
by Marshall Clow 14 Nov '18

14 Nov '18

On Wed, Nov 14, 2018 at 9:02 AM Edward Diener via Boost-users < boost-users(a)lists.boost.org> wrote: > On 11/14/2018 11:06 AM, Marshall Clow via Boost-users wrote: > > On Mon, Nov 12, 2018 at 4:30 PM Tom Kent via Boost-users > > <boost-users(a)lists.boost.org <mailto:boost-users@lists.boost.org>> > wrote: > > > > > > On Mon, Nov 12, 2018 at 9:36 AM Marshall Clow via Boost-users > > <boost-users(a)lists.boost.org <mailto:… [View More]boost-users@lists.boost.org>> > > wrote: > > > > The release candidates for the first 1.69.0 beta release are now > > available at: > > > > <https://dl.bintray.com/boostorg/beta/1.69.0.beta.1.rc1/source/> > > > > 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. > > > > > > toolset arch compile Link Execute > > msvc-8.0 32 FAIL X X > > msvc-8.0 64 FAIL 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 FAIL X X > > msvc-14.0 64 FAIL X X > > msvc-14.1 32 X X X > > msvc-14.1 64 X X X > > > > Compile means that the b2 command completed without errors > > 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. > > > > Full build logs can be found here: > > https://gist.github.com/teeks99/526cf2598d1697557e45e590ce9517be > > > > Lots of errors with msvc-8.0: > > > > compile-c-c++ > > > bin.v2\libs\log\build\msvc-8.0\release\link-static\threadapi-win32\threading-multi\trivial.obj > > trivial.cpp > > .\boost/parameter/aux_/arg_list.hpp(227) : error C2064: term does > > not evaluate to a function taking 1 arguments > > .\boost/parameter/aux_/arg_list.hpp(390) : see reference to > > class template instantiation > > 'boost::parameter::aux::arg_list<TaggedArg,Next>' being compiled > > > > If there is an easy way to fix arg_list.hpp that would be nice, > > but if this is the time to stop build 8.0, that's fine too. > > I have essentially backed out a fix on 'develop' for VC++8.0 which > intended to fix another problem with a multiple definitions linking > error, https://github.com/boostorg/mpl/pull/36. > > I would like to push this change to 'master'. It should fix your problem > above with VC++8.0. I will subsequently take another look at the > original fix and see if it can not be corrected. > If you're confident that this will fix the problem, then please do so. -- Marshall [View Less]

1 0

Re: [boost] [Boost-users] [release] Boost 1.69.0 Beta 1 Release Candidate 1
by Marshall Clow 14 Nov '18

14 Nov '18

On Wed, Nov 14, 2018 at 8:35 AM Edward Diener via Boost-users < boost-users(a)lists.boost.org> wrote: > On 11/14/2018 11:06 AM, Marshall Clow via Boost-users wrote: > > On Mon, Nov 12, 2018 at 4:30 PM Tom Kent via Boost-users > > <boost-users(a)lists.boost.org <mailto:boost-users@lists.boost.org>> > wrote: > > > > toolset arch compile Link Execute > > msvc-8.0 32 FAIL X X > > msvc-8.0 64 … [View More]

1 0

What is status of Boost.Sync?
by Mateusz Loskot 13 Nov '18

13 Nov '18

Hi, The library docs docs say it's been in Boost since 1.55. Boost master has no submodule for it. Boost develop has submodule for it If Sync was removed, why it is still in develop? If Sync was added, hence it is in develop, why the docs mention 1.55 and why it is not in master? What is the status of this thing? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

2 2