1.58.0 rc3 is now available
Release candidate files for 1.58.0 are available at: http://boost.cowic.de/rc/ * Since rc1, the changes that were causing the serialization libraries to fail to build on MSVC have been reverted. * Since rc2, the documentation for bind, and mem_fun. No code changes. 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_58_0_rc3.7z) = f7255aeb692c1c38fe761c32fb0d3ecd MD5 (boost_1_58_0_rc3.tar.bz2) = b8839650e61e9c1c0a89f371dd475546 MD5 (boost_1_58_0_rc3.tar.gz) = 5a5d5614d9a07672e1ab2a250b5defc5 MD5 (boost_1_58_0_rc3.zip) = b0605a9323f1e960f7434dbbd95a7a5c Thanks! -- The release managers P.S. Release notes are here: http://www.boost.org/users/history/version_1_58_0.html
On Tue, Apr 7, 2015 at 11:47 PM, Marshall Clow
Release candidate files for 1.58.0 are available at: http://boost.cowic.de/rc/
* Since rc1, the changes that were causing the serialization libraries to fail to build on MSVC have been reverted. * Since rc2, the documentation for bind, and mem_fun. No code changes.
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.
Still looks good on windows: toolset arch compile Link Execute msvc-8.0 32 X X X msvc-8.0 64 X 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 Compile means that the b2 command completed without errors Install means that the installers for the respective version were generated 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. Logs at: https://gist.github.com/teeks99/5d0120e5815d366f1e2e#file-boost_1_58_0-rc3-3... https://gist.github.com/teeks99/1ffa6c8efbf54a4d2005#file-boost_1_58_0-rc3-6... Tom
Building Boost 1.58.0-rc3 succeeded only partially. Success: Debian 7 with GCC 4.8.2 (in C++03 mode) with build-command: b2 -j4 --build-dir=/opt/build/test --build-type=complete --layout=versioned address-model=64 architecture=x86 install --prefix="/opt/install/test" toolset=gcc-4.8 cflags="-fPIC" cxxflags="-fPIC" dll-path="/opt/test/lib/x86_64-linux-gnu" Failure: Debian 7 with GCC 4.8.2 (in C++11 mode) with build-command: b2 -j4 --build-dir=/opt/build/test --build-type=complete --layout=versioned address-model=64 architecture=x86 install --prefix="/opt/install/test" toolset=gcc-4.8 cflags="-fPIC" cxxflags="-fPIC -std=c++11" dll-path="/opt/test/lib/x86_64-linux-gnu" The main-error seems to come from "Boost.Context" and the use of unknown "std::index_sequence": gcc.compile.c++ /opt/build/test/boost/bin.v2/libs/context/build/gcc-4.8/debug/link-static/threading-multi/execution_context.o In file included from libs/context/src/execution_context.cpp:11:0: ./boost/context/execution_context.hpp:202:52: error: ‘std::index_sequence’ has not been declared std::index_sequence< I ... >) { ^ ./boost/context/execution_context.hpp:202:66: error: expected ‘,’ or ‘...’ before ‘<’ token std::index_sequence< I ... >) { ^ ./boost/context/execution_context.hpp:219:52: error: ‘std::index_sequence’ has not been declared std::index_sequence< I ... >) { ^ ./boost/context/execution_context.hpp:219:66: error: expected ‘,’ or ‘...’ before ‘<’ token std::index_sequence< I ... >) { ^ ./boost/context/execution_context.hpp: In constructor ‘boost::context::execution_context::execution_context(StackAlloc, Fn&&, Args&& ...)’: ./boost/context/execution_context.hpp:267:39: error: ‘index_sequence_for’ is not a member of ‘std’ std::index_sequence_for< Args ... >() ) ) { ^ ./boost/context/execution_context.hpp:267:69: error: expected primary-expression before ‘...’ token std::index_sequence_for< Args ... >() ) ) { ^ ./boost/context/execution_context.hpp: In constructor ‘boost::context::execution_context::execution_context(boost::context::preallocated, StackAlloc, Fn&&, Args&& ...)’: ./boost/context/execution_context.hpp:275:39: error: ‘index_sequence_for’ is not a member of ‘std’ std::index_sequence_for< Args ... >() ) ) { ^ ./boost/context/execution_context.hpp:275:69: error: expected primary-expression before ‘...’ token std::index_sequence_for< Args ... >() ) ) { ^ Best regards, Deniz Am 08.04.2015 um 08:47 schrieb Marshall Clow:
Release candidate files for 1.58.0 are available at: http://boost.cowic.de/rc/
* Since rc1, the changes that were causing the serialization libraries to fail to build on MSVC have been reverted. * Since rc2, the documentation for bind, and mem_fun. No code changes.
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_58_0_rc3.7z) = f7255aeb692c1c38fe761c32fb0d3ecd MD5 (boost_1_58_0_rc3.tar.bz2) = b8839650e61e9c1c0a89f371dd475546 MD5 (boost_1_58_0_rc3.tar.gz) = 5a5d5614d9a07672e1ab2a250b5defc5 MD5 (boost_1_58_0_rc3.zip) = b0605a9323f1e960f7434dbbd95a7a5c
Thanks!
-- The release managers
P.S.Release notes are here: http://www.boost.org/users/history/version_1_58_0.html
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
On Thu, Apr 9, 2015 at 4:11 AM, Deniz Bahadir
Building Boost 1.58.0-rc3 succeeded only partially.
Success:
Debian 7 with GCC 4.8.2 (in C++03 mode) with build-command: b2 -j4 --build-dir=/opt/build/test --build-type=complete --layout=versioned address-model=64 architecture=x86 install --prefix="/opt/install/test" toolset=gcc-4.8 cflags="-fPIC" cxxflags="-fPIC" dll-path="/opt/test/lib/x86_64-linux-gnu"
Failure:
Debian 7 with GCC 4.8.2 (in C++11 mode) with build-command: b2 -j4 --build-dir=/opt/build/test --build-type=complete --layout=versioned address-model=64 architecture=x86 install --prefix="/opt/install/test" toolset=gcc-4.8 cflags="-fPIC" cxxflags="-fPIC -std=c++11" dll-path="/opt/test/lib/x86_64-linux-gnu"
The main-error seems to come from "Boost.Context" and the use of unknown "std::index_sequence":
std::index_sequence is a C++14 feature. -- Marshall
Am 09.04.2015 um 16:39 schrieb Marshall Clow:
On Thu, Apr 9, 2015 at 4:11 AM, Deniz Bahadir
mailto:dbahadir@benocs.com> wrote: Building Boost 1.58.0-rc3 succeeded only partially.
Success:
Debian 7 with GCC 4.8.2 (in C++03 mode) with build-command: b2 -j4 --build-dir=/opt/build/test --build-type=complete --layout=versioned address-model=64 architecture=x86 install --prefix="/opt/install/test" toolset=gcc-4.8 cflags="-fPIC" cxxflags="-fPIC" dll-path="/opt/test/lib/x86___64-linux-gnu"
Failure:
Debian 7 with GCC 4.8.2 (in C++11 mode) with build-command: b2 -j4 --build-dir=/opt/build/test --build-type=complete --layout=versioned address-model=64 architecture=x86 install --prefix="/opt/install/test" toolset=gcc-4.8 cflags="-fPIC" cxxflags="-fPIC -std=c++11" dll-path="/opt/test/lib/x86___64-linux-gnu"
The main-error seems to come from "Boost.Context" and the use of unknown "std::index_sequence":
std::index_sequence is a C++14 feature.
The question is then: Why is it used when I only enable C++11 features? I suppose, GCC 4.8(.2) is too old to support std::index_sequence. (Or is it the bundled stdlibc++?) When using C++14 mode ("cxxflags=-fPIC -std=c++1y") the same errors occur. Deniz
On Thu, Apr 9, 2015 at 8:15 AM, Deniz Bahadir
Am 09.04.2015 um 16:39 schrieb Marshall Clow:
On Thu, Apr 9, 2015 at 4:11 AM, Deniz Bahadir
mailto:dbahadir@benocs.com> wrote: Building Boost 1.58.0-rc3 succeeded only partially.
Success:
Debian 7 with GCC 4.8.2 (in C++03 mode) with build-command: b2 -j4 --build-dir=/opt/build/test --build-type=complete --layout=versioned address-model=64 architecture=x86 install --prefix="/opt/install/test" toolset=gcc-4.8 cflags="-fPIC" cxxflags="-fPIC" dll-path="/opt/test/lib/x86___64-linux-gnu"
Failure:
Debian 7 with GCC 4.8.2 (in C++11 mode) with build-command: b2 -j4 --build-dir=/opt/build/test --build-type=complete --layout=versioned address-model=64 architecture=x86 install --prefix="/opt/install/test" toolset=gcc-4.8 cflags="-fPIC" cxxflags="-fPIC -std=c++11" dll-path="/opt/test/lib/x86___ 64-linux-gnu"
The main-error seems to come from "Boost.Context" and the use of unknown "std::index_sequence":
std::index_sequence is a C++14 feature.
The question is then: Why is it used when I only enable C++11 features?
My guess would be "a bug".
I suppose, GCC 4.8(.2) is too old to support std::index_sequence. (Or is it the bundled stdlibc++?) When using C++14 mode ("cxxflags=-fPIC -std=c++1y") the same errors occur.
It would not surprise me if gcc 4.8.x did not support index_sequence. And yes, it would be the libstdc++ that comes with the compiler, not the compiler itself. FWIW, index_sequence *is* implemented in gcc 4.9.2, but it is only available post-c++11. -- Marshall
It would not surprise me if gcc 4.8.x did not support index_sequence. And yes, it would be the libstdc++ that comes with the compiler, not the compiler itself.
FWIW, index_sequence *is* implemented in gcc 4.9.2, but it is only available post-c++11.
-- Marshall
Not sure if this is relevent, but I received the same error on VS2015 CTP 6. I changed the code to std::integer_sequence< std::size_t, I ... > to get around it. On a related note, on CTP6, Microsoft has changed the include paths for the CRT. For some reason some boost build generated files with names like 'b2_msvc_14.0_vcvarsall_amd64.cmd' were not regenerating after I upgraded to CTP6 which resulted in a stale INCLUDE environment variable an consequently, a failed build. Manually deleting the files corrected the problem. -- chris
2015-04-09 17:54 GMT+02:00 Marshall Clow
My guess would be "a bug".
unfortunately boost is missing a test macro for std::index_sequence see - http://lists.boost.org/Archives/boost/2015/02/220149.php
participants (5)
-
Chris Glover
-
Deniz Bahadir
-
Marshall Clow
-
Oliver Kowalke
-
Tom Kent