The release candidates for the 1.61.0 release are now available at: https://dl.bintray.com/boostorg/beta/boost_1_65_0_beta1_rc1.7z https://dl.bintray.com/boostorg/beta/boost_1_65_0_beta1_rc1.tar.bz2 https://dl.bintray.com/boostorg/beta/boost_1_65_0_beta1_rc1.tar.gz https://dl.bintray.com/boostorg/beta/boost_1_65_0_beta1_rc1.zip The SHA256 checksums are as follows: cd7429340bb4aae38e0ad2e9f59c39e66335302c41577956123e55fc1e2a28ee boost_1_65_0_beta1_rc1.7z fda076f7b3c994524d9cd41926c72f4a9b7c017bef310a055956fdd0bed7c358 boost_1_65_0_beta1_rc1.tar.bz2 0d1473041f7a9fa9ce1e256c870cc52af6f98abf723cf4f1ac61c2b45f45d38a boost_1_65_0_beta1_rc1.tar.gz f45bbb75b84cdc0c66f8a571d77c518cfbac076d7a6fc7937c4812f0f242a792 boost_1_65_0_beta1_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. Thanks! -- The release managers
On Sun, Jul 9, 2017 at 1:04 AM, Marshall Clow via Boost-users < boost-users@lists.boost.org> wrote:
The release candidates for the 1.61.0 release are now available at:
https://dl.bintray.com/boostorg/beta/boost_1_65_0_beta1_rc1.7z https://dl.bintray.com/boostorg/beta/boost_1_65_0_beta1_rc1.tar.bz2 https://dl.bintray.com/boostorg/beta/boost_1_65_0_beta1_rc1.tar.gz https://dl.bintray.com/boostorg/beta/boost_1_65_0_beta1_rc1.zip
The SHA256 checksums are as follows:
cd7429340bb4aae38e0ad2e9f59c39e66335302c41577956123e55fc1e2a28ee boost_1_65_0_beta1_rc1.7z fda076f7b3c994524d9cd41926c72f4a9b7c017bef310a055956fdd0bed7c358 boost_1_65_0_beta1_rc1.tar.bz2 0d1473041f7a9fa9ce1e256c870cc52af6f98abf723cf4f1ac61c2b45f45d38a boost_1_65_0_beta1_rc1.tar.gz f45bbb75b84cdc0c66f8a571d77c518cfbac076d7a6fc7937c4812f0f242a792 boost_1_65_0_beta1_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.
B2 fails immediately (showstopper!!!) on windows for all tested visual studio compilers (8.0-14.1) when running with --build-type=complete, such as: b2 -j%NUMBER_OF_PROCESSORS% --without-mpi --build-type=complete toolset=msvc-8.0 address-model=32 architecture=x86 --prefix=.\ --libdir=lib32-msvc-8.0 --includedir=garbage_headers install with the error: error: link=shared together with runtime-link=static is not allowed error: such property combination is either impossible error: or too dangerious to be of any use
Tom Kent wrote:
B2 fails immediately (showstopper!!!) on windows for all tested visual studio compilers (8.0-14.1) when running with --build-type=complete, such as:
b2 -j%NUMBER_OF_PROCESSORS% --without-mpi --build-type=complete toolset=msvc-8.0 address-model=32 architecture=x86 --prefix=.\ --libdir=lib32-msvc-8.0 --includedir=garbage_headers install
with the error:
error: link=shared together with runtime-link=static is not allowed error: such property combination is either impossible error: or too dangerious to be of any use
Confirmed, minimal repro is b2 --with-stacktrace --build-type=complete stage
Tom Kent wrote:
B2 fails immediately (showstopper!!!) on windows for all tested visual studio compilers (8.0-14.1) when running with --build-type=complete, such as:
b2 -j%NUMBER_OF_PROCESSORS% --without-mpi --build-type=complete toolset=msvc-8.0 address-model=32 architecture=x86 --prefix=.\ --libdir=lib32-msvc-8.0 --includedir=garbage_headers install
with the error:
error: link=shared together with runtime-link=static is not allowed error: such property combination is either impossible error: or too dangerious to be of any use
Confirmed, minimal repro is
b2 --with-stacktrace --build-type=complete stage
Patch: diff --git a/build/Jamfile.v2 b/build/Jamfile.v2 index 0e9720a..12c0edb 100644 --- a/build/Jamfile.v2 +++ b/build/Jamfile.v2 @@ -11,8 +11,8 @@ project <target-os>linux:<cxxflags>"-fvisibility=hidden" ; -lib dl : : <link>shared ; -lib gcc_s : : <link>shared ; +lib dl : : <link>shared <runtime-link>shared ; +lib gcc_s : : <link>shared <runtime-link>shared ; lib Dbgeng ; lib ole32 ;
Confirmed, minimal repro is
b2 --with-stacktrace --build-type=complete stage
Patch: ...
This is actually fixed in Stacktrace's master branch: https://github.com/boostorg/stacktrace/commit/9c1ed7fc95350bd7a0540ef600df2a... but the superproject master doesn't seem to have picked up this change.
2017-07-09 21:18 GMT+03:00 Peter Dimov via Boost
Confirmed, minimal repro is
b2 --with-stacktrace --build-type=complete stage
Patch:
...
This is actually fixed in Stacktrace's master branch:
https://github.com/boostorg/stacktrace/commit/9c1ed7fc95350bd7a0540ef600df2a...
but the superproject master doesn't seem to have picked up this change.
I've merged it to master only today (sorry for the delay). Looks like header only Boost.Coroutine2 wishes to autolink with a boost_coroutine2 library (tried to build this example https://github.com/apolukhin/Boost-Cookbook/tree/second_edition/Chapter11/09...) : LINK : fatal error LNK1104: cannot open file 'libboost_coroutine2-vc140-mt-gd-1_65.lib' NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\amd64\link.EXE"' : return code '0x450' -- Best regards, Antony Polukhin
participants (4)
-
Antony Polukhin -
Marshall Clow -
Peter Dimov -
Tom Kent