[release] Boost 1.69.0 Beta 1 Release Candidate 1
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/> The release notes are not yet available. The updated documentation is not yet available. [ They will be available in a day or two. ] The SHA256 checksums are as follows: db6b346389714647490d6503db881e4178dd8cd498f850999bebf72cacd4c4ed boost_1_69_0_b1_rc1.7z d128c82351becbd37a02b9b4818994d3f66ff8bdbc0a18838206f4c070db97af boost_1_69_0_b1_rc1.tar.bz2 4df6262db53cfd0d0f934cb126f7e48e94872fe4441cbac6bf72a43bfb136a45 boost_1_69_0_b1_rc1.tar.gz e2908e33cc15f92cda06ddde6a3da43b18967a83105355571fc3cf6e75820c7f boost_1_69_0_b1_rc1.zip 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 Boost Release Managers
On Mon, Nov 12, 2018 at 7:36 AM Marshall Clow <mclow.lists@gmail.com> 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.
I have built the RC on Mac OS X 10.11 using Apple LLVM version 8.0.0 (clang-800.0.42.1) successfully while specifiying c++03/11/14/1z -- Marshall
On Mon, Nov 12, 2018 at 7:36 AM Marshall Clow <mclow.lists@gmail.com> 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.
I have built the RC on Mac OS X 10.13 using Apple LLVM version 10.0.0 (clang-1000.10.44.4) successfully while specifying c++03/11/14, but failed when specifying c++17/2a, because the Python 2.7 headers shipped with Mac OS 10.13 use the "register" keyword: In file included from /System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/Python.h:85: /System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/unicodeobject.h:534:5: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister] register PyObject *obj, /* Object */ ^~~~~~~~~ -- Marshall
On Mon, Nov 12, 2018 at 7:36 AM Marshall Clow <mclow.lists@gmail.com> 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.
I have built the RC on Mac OS X 10.13 using a recent trunk build of clang (version 8.0.0 (trunk 346609)) successfully while specifying c++03/11/14, but failed when specifying c++17/2a, because the Python 2.7 headers shipped with Mac OS 10.13 use the "register" keyword: In file included from /System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/Python.h:85: /System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/unicodeobject.h:534:5: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister] register PyObject *obj, /* Object */ ^~~~~~~~~ (same results as with Apple's clang) -- Marshall
On Mon, Nov 12, 2018 at 9:36 AM Marshall Clow via Boost-users < 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/>
For the last beta release, this was: https://dl.bintray.com/boostorg/beta/1.68.0.beta1.rc2/source/ It isn't crucial, but it would be nice for my scripts if we could keep the same paths (beta.1 vs. beta1).
The release notes are not yet available. The updated documentation is not yet available. [ They will be available in a day or two. ]
Does that mean there will definitely be another RC before the beta? Or are notes only required for the release?
The SHA256 checksums are as follows:
db6b346389714647490d6503db881e4178dd8cd498f850999bebf72cacd4c4ed boost_1_69_0_b1_rc1.7z d128c82351becbd37a02b9b4818994d3f66ff8bdbc0a18838206f4c070db97af boost_1_69_0_b1_rc1.tar.bz2 4df6262db53cfd0d0f934cb126f7e48e94872fe4441cbac6bf72a43bfb136a45 boost_1_69_0_b1_rc1.tar.gz e2908e33cc15f92cda06ddde6a3da43b18967a83105355571fc3cf6e75820c7f boost_1_69_0_b1_rc1.zip
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. 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. Tom
Hi,
Am 13.11.2018 um 01:30 schrieb Tom Kent via Boost-users <boost-users@lists.boost.org>:
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 still have to use VS2005, so I would like to see this compiler still being supported. 73, Mario
On Tue, Nov 13, 2018 at 12:50 AM Klebsch, Mario via Boost-users <boost-users@lists.boost.org> wrote:
I still have to use VS2005, so I would like to see this compiler still being supported.
Just for information purposes, for how many more years do you think VS2005 should be generally supported? Thanks
On Tue, Nov 13, 2018 at 10:53 AM Vinnie Falco via Boost-users <boost-users@lists.boost.org> wrote:
On Tue, Nov 13, 2018 at 12:50 AM Klebsch, Mario via Boost-users <boost-users@lists.boost.org> wrote:
I still have to use VS2005, so I would like to see this compiler still being supported.
Just for information purposes, for how many more years do you think VS2005 should be generally supported?
Going the way of the mainframes and dinosaurs, methinks. Years ago, I might have considered 2008 to be the bare minimum point of entry; today, perhaps 2010 or even 2012. Food for thought...
Thanks _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users
AMDG On 11/12/2018 05:30 PM, Tom Kent via Boost-users wrote:
<snip> Also numerous errors for many (all dlls?) of the libraries with msvc-14.0. They all look something like this:
<snip> 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" )
<snip>
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.
I don't think anything has changed in Boost.Build that would affect this. Have you checked your msvc installation? I would suggest checking whether msvc-setup.bat is out-dated, but you're running a clean build here, right? Can you try forcing the original setup scripts: using msvc : 14.0 : : <rewrite-setup-scripts>off ; In Christ, Steven Watanabe
On Mon, Nov 12, 2018 at 4:30 PM Tom Kent via Boost-users < boost-users@lists.boost.org> wrote:
On Mon, Nov 12, 2018 at 9:36 AM Marshall Clow via Boost-users < 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.
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)
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@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@lists.boost.org <mailto: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.
Nothing has changed in boost/parameter/aux_/arg_list.hpp since 1.68 on the 'master' branch.
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@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@lists.boost.org <mailto: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.
This is a result of a change in MPL for VC++8. I will back out this change.
On Wed, Nov 14, 2018 at 8:35 AM Edward Diener via Boost-users < boost-users@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@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 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
[snip]
Lots of errors with msvc-8.0:
[snip]
This is a result of a change in MPL for VC++8. I will back out this change.
Appreciated. Please test locally, and we'll watch the bots. (Looks like we have two MSVC-8 bots) -- Marshall
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@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@lists.boost.org <mailto: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.
On Wed, Nov 14, 2018 at 9:02 AM Edward Diener via Boost-users < boost-users@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@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@lists.boost.org <mailto: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
On 11/14/2018 12:39 PM, Marshall Clow via Boost-users wrote:
On Wed, Nov 14, 2018 at 9:02 AM Edward Diener via Boost-users <boost-users@lists.boost.org <mailto:boost-users@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@lists.boost.org <mailto:boost-users@lists.boost.org> <mailto:boost-users@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@lists.boost.org <mailto:boost-users@lists.boost.org> <mailto:boost-users@lists.boost.org <mailto: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.
I have updated 'master' with the backed out change. This should fix the problems you are seeing for the release candidate with vc++8.0. I will take another look at the original fix and if I am sure I can fix the original fix correctly, which is trivial codewise, I will do so for 1.69 if it is wished.
On Wed, Nov 14, 2018 at 10:06 AM Marshall Clow via Boost-users < boost-users@lists.boost.org> wrote:
On Mon, Nov 12, 2018 at 4:30 PM Tom Kent via Boost-users < boost-users@lists.boost.org> wrote:
On Mon, Nov 12, 2018 at 9:36 AM Marshall Clow via Boost-users < 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.
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?
This turned out to be something with the (Virtual) machine, I was able to run without issue on another machine. Sorry for that red-herring. Rebuilding binaries now. Tom
participants (7)
-
Edward Diener -
Klebsch, Mario -
Marshall Clow -
Michael Powell -
Steven Watanabe -
Tom Kent -
Vinnie Falco