Boost 1.65.0 Beta 1 Release Candidate 2
The second release candidates for the 1.65.0 beta release are now available at: https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1... https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1... https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1... https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1... The SHA256 checksums are as follows: d54d29568c4e4933cbfe40a292b6cb84a7f68121e34f6a83f7d0f7c652b6b2d8 boost_1_65_0_beta1_rc2.7z 092676557513e992347d30dd0cd058fb8af2a401e5da4f4413f5b577852d726b boost_1_65_0_beta1_rc2.tar.bz2 31fa3c807e2205e18f7d5c74f77f540677f7b0937af1e37f595c137e1e87bf84 boost_1_65_0_beta1_rc2.tar.gz 83c8d8b76fa9591572226a1a49fd191d76db3011b52b907cbbc8d37d46213bd2 boost_1_65_0_beta1_rc2.zip This RC contains a single fix to the stacktrace library. 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. Thanks! -- The release managers
Le 11.07.17 à 02:14, Marshall Clow via Boost-users a écrit :
The second release candidates for the 1.65.0 beta release are now available at:
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1...
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1...
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1...
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1...
The SHA256 checksums are as follows:
d54d29568c4e4933cbfe40a292b6cb84a7f68121e34f6a83f7d0f7c652b6b2d8 boost_1_65_0_beta1_rc2.7z 092676557513e992347d30dd0cd058fb8af2a401e5da4f4413f5b577852d726b boost_1_65_0_beta1_rc2.tar.bz2 31fa3c807e2205e18f7d5c74f77f540677f7b0937af1e37f595c137e1e87bf84 boost_1_65_0_beta1_rc2.tar.gz 83c8d8b76fa9591572226a1a49fd191d76db3011b52b907cbbc8d37d46213bd2 boost_1_65_0_beta1_rc2.zip
This RC contains a single fix to the stacktrace library.
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.
Thanks!
-- The release managers
Hi,
I have this error during the build on OSX. Built with:
./b2 cxxflags="-std=c++11 -stdlib=libc++" linkflags="-stdlib=libc++"
--without-log --layout=versioned install
...on 14200th target...
common.mkdir bin.v2/libs/fiber/build/darwin-4.2.1/release/threading-multi
common.mkdir
bin.v2/libs/fiber/build/darwin-4.2.1/release/threading-multi/numa
darwin.compile.c++
bin.v2/libs/fiber/build/darwin-4.2.1/release/threading-multi/numa/pin_thread.o
libs/fiber/src/numa/pin_thread.cpp:23:10: warning: pin_thread() not
supported [-W#pragma-messages]
# pragma message "pin_thread() not supported"
^
1 warning generated.
darwin.compile.c++
bin.v2/libs/fiber/build/darwin-4.2.1/release/threading-multi/numa/topology.o
libs/fiber/src/numa/topology.cpp:23:10: warning: topology() not
supported [-W#pragma-messages]
# pragma message "topology() not supported"
^
libs/fiber/src/numa/topology.cpp:27:14: error: use of undeclared
identifier 'topology'; did you mean 'fibers::numa::topology'?
std::vector< topology > topology() {
^~~~~~~~
fibers::numa::topology
./boost/fiber/numa/topology.hpp:38:21: note: 'fibers::numa::topology'
declared here
std::vector< node > topology();
^
libs/fiber/src/numa/topology.cpp:27:14: error: template argument for
template type parameter must be a type
std::vector< topology > topology() {
^~~~~~~~
/Applications/Xcode8.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/vector:456:17:
note: template parameter is declared here
template
On Tue, Jul 11, 2017 at 4:06 AM, Raffi Enficiaud via Boost-users < boost-users@lists.boost.org> wrote:
Le 11.07.17 à 02:14, Marshall Clow via Boost-users a écrit :
The second release candidates for the 1.65.0 beta release are now
available at:
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/ boost_1_65_0_beta1_rc2.7z
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/ boost_1_65_0_beta1_rc2.tar.bz2
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/ boost_1_65_0_beta1_rc2.tar.gz
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/ boost_1_65_0_beta1_rc2.zip
The SHA256 checksums are as follows:
d54d29568c4e4933cbfe40a292b6cb84a7f68121e34f6a83f7d0f7c652b6b2d8 boost_1_65_0_beta1_rc2.7z 092676557513e992347d30dd0cd058fb8af2a401e5da4f4413f5b577852d726b boost_1_65_0_beta1_rc2.tar.bz2 31fa3c807e2205e18f7d5c74f77f540677f7b0937af1e37f595c137e1e87bf84 boost_1_65_0_beta1_rc2.tar.gz 83c8d8b76fa9591572226a1a49fd191d76db3011b52b907cbbc8d37d46213bd2 boost_1_65_0_beta1_rc2.zip
This RC contains a single fix to the stacktrace library.
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.
Thanks!
-- The release managers
Hi,
I have this error during the build on OSX. Built with: ./b2 cxxflags="-std=c++11 -stdlib=libc++" linkflags="-stdlib=libc++" --without-log --layout=versioned install
...on 14200th target... common.mkdir bin.v2/libs/fiber/build/darwin-4.2.1/release/threading-multi common.mkdir bin.v2/libs/fiber/build/darwin-4.2.1/release/threading- multi/numa darwin.compile.c++ bin.v2/libs/fiber/build/darwin-4.2.1/release/threading- multi/numa/pin_thread.o libs/fiber/src/numa/pin_thread.cpp:23:10: warning: pin_thread() not supported [-W#pragma-messages] # pragma message "pin_thread() not supported" ^ 1 warning generated. darwin.compile.c++ bin.v2/libs/fiber/build/darwin-4.2.1/release/threading- multi/numa/topology.o libs/fiber/src/numa/topology.cpp:23:10: warning: topology() not supported [-W#pragma-messages] # pragma message "topology() not supported"
Given these two messages, I suspect that is deliberate. I see that too in my tests. -- Marshall
On Mon, Jul 10, 2017 at 7:14 PM, Marshall Clow via Boost-users < boost-users@lists.boost.org> wrote:
The second release candidates for the 1.65.0 beta release are now available at:
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/ source/boost_1_65_0_beta1_rc2.7z https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/ source/boost_1_65_0_beta1_rc2.tar.bz2 https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/ source/boost_1_65_0_beta1_rc2.tar.gz https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/ source/boost_1_65_0_beta1_rc2.zip
The SHA256 checksums are as follows:
d54d29568c4e4933cbfe40a292b6cb84a7f68121e34f6a83f7d0f7c652b6b2d8 boost_1_65_0_beta1_rc2.7z 092676557513e992347d30dd0cd058fb8af2a401e5da4f4413f5b577852d726b boost_1_65_0_beta1_rc2.tar.bz2 31fa3c807e2205e18f7d5c74f77f540677f7b0937af1e37f595c137e1e87bf84 boost_1_65_0_beta1_rc2.tar.gz 83c8d8b76fa9591572226a1a49fd191d76db3011b52b907cbbc8d37d46213bd2 boost_1_65_0_beta1_rc2.zip
This RC contains a single fix to the stacktrace library.
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.
Builds look good on windows, Visual Studio 8.0 - 14.1, 32&64 bit. 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 msvc-14.0 32 X X X msvc-14.0 64 X 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 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. Tom
On Mon, Jul 10, 2017 at 8:14 PM, Marshall Clow via Boost-users
The second release candidates for the 1.65.0 beta release are now available at:
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1...
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1...
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1...
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1...
Beta.1 or Beta.2?
The SHA256 checksums are as follows:
d54d29568c4e4933cbfe40a292b6cb84a7f68121e34f6a83f7d0f7c652b6b2d8 boost_1_65_0_beta1_rc2.7z 092676557513e992347d30dd0cd058fb8af2a401e5da4f4413f5b577852d726b boost_1_65_0_beta1_rc2.tar.bz2 31fa3c807e2205e18f7d5c74f77f540677f7b0937af1e37f595c137e1e87bf84 boost_1_65_0_beta1_rc2.tar.gz 83c8d8b76fa9591572226a1a49fd191d76db3011b52b907cbbc8d37d46213bd2 boost_1_65_0_beta1_rc2.zip
This RC contains a single fix to the stacktrace library.
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.
Thanks!
-- The release managers
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users
On Tue, Jul 11, 2017 at 11:06 AM, Michael Powell via Boost-users < boost-users@lists.boost.org> wrote:
The second release candidates for the 1.65.0 beta release are now available at:
On Mon, Jul 10, 2017 at 8:14 PM, Marshall Clow via Boost-users
wrote: source/boost_1_65_0_beta1_rc2.7z source/boost_1_65_0_beta1_rc2.tar.bz2
source/boost_1_65_0_beta1_rc2.tar.gz
source/boost_1_65_0_beta1_rc2.zip
Beta.1 or Beta.2?
Beta1 release candidate 2. We haven't reached Beta1 yet. -- Marshall
On 07/11/2017 02:14 AM, Marshall Clow via Boost-users wrote:
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.
Stacktrace fails to build on armv7l in openSUSE Factory, full build log available at, https://build.opensuse.org/package/live_build_log/home:adamm:branches:devel:...
[ 3697s] In file included from ./boost/stacktrace/detail/collect_unwind.ipp:17:0, [ 3697s] from ./boost/stacktrace/safe_dump_to.hpp:209, [ 3697s] from ./boost/stacktrace/frame.hpp:20, [ 3697s] from ./boost/stacktrace/detail/frame_unwind.ipp:15, [ 3697s] from libs/stacktrace/build/../src/addr2line.cpp:10: [ 3697s] ./boost/stacktrace/detail/collect_unwind.ipp: In function '_Unwind_Reason_Code boost::stacktrace::detail::unwind_callback(_Unwind_Context*, void*)': [ 3697s] ./boost/stacktrace/detail/collect_unwind.ipp:32:18: error: expected id-expression before '(' token [ 3697s] return ::_Unwind_GetIP(context) ? ::_URC_NO_REASON : ::_URC_END_OF_STACK; [ 3697s] ^ [ 3697s] ./boost/stacktrace/detail/collect_unwind.ipp:36:11: error: expected id-expression before '(' token [ 3697s] ::_Unwind_GetIP(context) [ 3697s] ^ [ 3697s] ...skipped
libboost_stacktrace_addr2line.so.1.65.0 for lack of addr2line.o...
- Adam
2017-07-13 16:16 GMT+03:00 Adam Majer via Boost-users
On 07/11/2017 02:14 AM, Marshall Clow via Boost-users wrote:
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.
Stacktrace fails to build on armv7l in openSUSE Factory,
full build log available at,
https://build.opensuse.org/package/live_build_log/home:adamm:branches:devel:...
[ 3697s] In file included from ./boost/stacktrace/detail/collect_unwind.ipp:17:0, [ 3697s] from ./boost/stacktrace/safe_dump_to.hpp:209, [ 3697s] from ./boost/stacktrace/frame.hpp:20, [ 3697s] from ./boost/stacktrace/detail/frame_unwind.ipp:15, [ 3697s] from libs/stacktrace/build/../src/addr2line.cpp:10: [ 3697s] ./boost/stacktrace/detail/collect_unwind.ipp: In function '_Unwind_Reason_Code boost::stacktrace::detail::unwind_callback(_Unwind_Context*, void*)': [ 3697s] ./boost/stacktrace/detail/collect_unwind.ipp:32:18: error: expected id-expression before '(' token [ 3697s] return ::_Unwind_GetIP(context) ? ::_URC_NO_REASON : ::_URC_END_OF_STACK; [ 3697s] ^ [ 3697s] ./boost/stacktrace/detail/collect_unwind.ipp:36:11: error: expected id-expression before '(' token [ 3697s] ::_Unwind_GetIP(context) [ 3697s] ^ [ 3697s] ...skipped
libboost_stacktrace_addr2line.so.1.65.0 for lack of addr2line.o... - Adam
Probably fixed it in here https://github.com/boostorg/stacktrace/commit/f853dbfc69ec7d02dde1cd43dc9b1b... Please, try out the patch. -- Best regards, Antony Polukhin
On 07/15/2017 04:57 PM, Antony Polukhin via Boost-users wrote:
Probably fixed it in here https://github.com/boostorg/stacktrace/commit/f853dbfc69ec7d02dde1cd43dc9b1b... Please, try out the patch.
Yes, compilation is fixed with this commit. Thank you! - Adam
Le 11.07.17 à 02:14, Marshall Clow via Boost-users a écrit :
The second release candidates for the 1.65.0 beta release are now available at:
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1...
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1... https://dl..bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta...
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1...
https://dl.bintray.com/boostorg/beta/1.65.0.beta.1/source/boost_1_65_0_beta1...
The SHA256 checksums are as follows:
d54d29568c4e4933cbfe40a292b6cb84a7f68121e34f6a83f7d0f7c652b6b2d8 boost_1_65_0_beta1_rc2.7z 092676557513e992347d30dd0cd058fb8af2a401e5da4f4413f5b577852d726b boost_1_65_0_beta1_rc2.tar.bz2 31fa3c807e2205e18f7d5c74f77f540677f7b0937af1e37f595c137e1e87bf84 boost_1_65_0_beta1_rc2.tar.gz 83c8d8b76fa9591572226a1a49fd191d76db3011b52b907cbbc8d37d46213bd2 boost_1_65_0_beta1_rc2.zip
This RC contains a single fix to the stacktrace library.
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.
Hi, I still cannot build boost.python on Windows x64: the output folder is completely empty (see below, tried for VS2015x64). I had this issue for the previous release if my memory is correct, and I believe this is due to the fact that the target system has several versions of Python. The target system has: - C:\Python27 - C:\Python34 - C:\Python36 How can I specify which version of Python I want to use, preferably from the command line? Thanks, Raffi ---------------------------------------------------------- PS D:\Projects-raffi\sw_thirdparties\visual2015x64\boost_1_65_0_src> & python Python 2.7.6 (default, Nov 10 2013, 19:24:24) [MSC v.1500 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information.
---------------------------------------------------------- PS D:\Projects-raffi\sw_thirdparties\visual2015x64\boost_1_65_0_src> & .\b2.exe --prefix=d:\tmp\boost_1_65_0 toolset=msvc-14.0 --layout=versioned --bu ild-type=complete --with-python -j 4 address-model=64 threading=multi runtime-link=shared Performing configuration checks - 32-bit : yes (cached) - arm : no (cached) - mips1 : no (cached) - power : no (cached) - sparc : no (cached) - x86 : yes (cached) Building the Boost C++ Libraries. - symlinks supported : no (cached) - junctions supported : yes (cached) - hardlinks supported : yes (cached) Component configuration: - atomic : not building - chrono : not building - container : not building - context : not building - coroutine : not building - date_time : not building - exception : not building - fiber : not building - filesystem : not building - graph : not building - graph_parallel : not building - iostreams : not building - locale : not building - log : not building - math : not building - metaparse : not building - mpi : not building - program_options : not building - python : building - random : not building - regex : not building - serialization : not building - signals : not building - stacktrace : not building - system : not building - test : not building - thread : not building - timer : not building - type_erasure : not building - wave : not building ...found 1 target... The Boost C++ Libraries were successfully built! The following directory should be added to compiler include paths: D:\Projects-raffi\sw_thirdparties\visual2015x64\boost_1_65_0_src The following directory should be added to linker library paths: D:\Projects-raffi\sw_thirdparties\visual2015x64\boost_1_65_0_src\stage\lib PS D:\Projects-raffi\sw_thirdparties\visual2015x64\boost_1_65_0_src>
participants (7)
-
Adam Majer
-
Antony Polukhin
-
Marshall Clow
-
Michael Powell
-
Oliver Kowalke
-
Raffi Enficiaud
-
Tom Kent