Discussion:
[boost] Boost 1.65.0 Beta 1 Release Candidate 1
Marshall Clow via Boost
2017-07-09 06:04:31 UTC
Permalink
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

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Tom Kent via Boost
2017-07-09 13:14:55 UTC
Permalink
On Sun, Jul 9, 2017 at 1:04 AM, Marshall Clow via Boost-users <
Post by Marshall Clow via Boost
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
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

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Peter Dimov via Boost
2017-07-09 18:05:58 UTC
Permalink
Post by Tom Kent via Boost
B2 fails immediately (showstopper!!!) on windows for all tested visual
studio compilers (8.0-14.1) when running with --build-type=complete, such
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
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


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Peter Dimov via Boost
2017-07-09 18:13:18 UTC
Permalink
Post by Peter Dimov via Boost
Post by Tom Kent via Boost
B2 fails immediately (showstopper!!!) on windows for all tested visual
studio compilers (8.0-14.1) when running with --build-type=complete,
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
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 ;


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Peter Dimov via Boost
2017-07-09 18:18:47 UTC
Permalink
Post by Peter Dimov via Boost
Confirmed, minimal repro is
b2 --with-stacktrace --build-type=complete stage
...

This is actually fixed in Stacktrace's master branch:

https://github.com/boostorg/stacktrace/commit/9c1ed7fc95350bd7a0540ef600df2a715271aa78

but the superproject master doesn't seem to have picked up this change.


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Antony Polukhin via Boost
2017-07-09 19:07:55 UTC
Permalink
Post by Peter Dimov via Boost
Post by Peter Dimov via Boost
Confirmed, minimal repro is
b2 --with-stacktrace --build-type=complete stage
...
https://github.com/boostorg/stacktrace/commit/9c1ed7fc95350bd7a0540ef600df2a715271aa78
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_coroutines)
:

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

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Joshua Berne via Boost
2017-07-09 13:27:31 UTC
Permalink
Hi,

I've been playing aournd with boost coroutines2 and maybe I'm just
confused about where this project is, but with 1.65 coroutines2 doesn't
seem to be buildable out of the box any longer:

I've tried looking through mailing list archives for anything about the
status of coroutine2 to no avail, and coroutine still spits out warnings
to use coroutine2 when used. I'm not sure where in the build system
things hook in to fix this.

Here's the output on my system:
***@Bugg:~/tmp$ tar xzf boost_1_65_0_beta1_rc1.tar.gz
***@Bugg:~/tmp$ cd boost_1_65_0/
***@Bugg:~/tmp/boost_1_65_0$ ./bootstrap.sh --with-toolset=clang
Building Boost.Build engine with toolset clang...
tools/build/src/engine/bin.linuxx86_64/b2
Detecting Python version... 2.7
Detecting Python root... /usr
Unicode/ICU support for Boost.Regex?... not found.
Generating Boost.Build configuration in project-config.jam...

Bootstrapping is done. To build, run:

./b2

To adjust configuration, edit 'project-config.jam'.
Further information:

- Command line help:
./b2 --help

- Getting started guide:
http://www.boost.org/more/getting_started/unix-variants.html

- Boost.Build documentation:
http://www.boost.org/build/doc/html/index.html

***@Bugg:~/tmp/boost_1_65_0$ ./b2 --with-coroutine2
error: wrong library name 'coroutine2' in the --with-<library> option.

Thanks.

- Josh


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Oliver Kowalke via Boost
2017-07-09 14:25:41 UTC
Permalink
Post by Joshua Berne via Boost
Hi,
I've been playing aournd with boost coroutines2 and maybe I'm just
confused about where this project is, but with 1.65 coroutines2 doesn't
boost.coroutine2 is a header-only lib - b2 --with-<library> would not work
Post by Joshua Berne via Boost
I've tried looking through mailing list archives for anything about the
status of coroutine2 to no avail, and coroutine still spits out warnings to
use coroutine2 when used. I'm not sure where in the build system things
hook in to fix this.
boost.coroutine is deprecated - but you can disable the warning (see
documentation)
boost.coroutine2 requires some C++11 features (you need to apply
cxxflags="-std=c++11" or equivalent)

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Joshua Berne via Boost
2017-07-09 15:02:41 UTC
Permalink
It is header only but it does depend on a number of non-header-only
libraries.

With 1.64.0, b2 --with-coroutine2 did work and triggered the building of
thread, chrono, system, and context (and obviously no coroutine2 library
since b2 is header only). If this change is intentional because
coroutine2 is header-only then that's fine, but when header-only libraries
depend on non-header only libraries it was certainly useful to me to be
able to trigger their dependancies to build with b2 using --with-<x>
instead of having to manually figure out those dependancies and maintain
that list with future boost releases.


I'm aware of the ability to disable the warning. The documentation isn't
even needed since the warning itself provides instructions on how to
disable it, but I'm targetting c++17 so everything in the documentation
seems to suggest that I should focus on using coroutine2.

- Josh
Post by Oliver Kowalke via Boost
Post by Joshua Berne via Boost
Hi,
I've been playing aournd with boost coroutines2 and maybe I'm just
confused about where this project is, but with 1.65 coroutines2 doesn't
boost.coroutine2 is a header-only lib - b2 --with-<library> would not work
Post by Joshua Berne via Boost
I've tried looking through mailing list archives for anything about the
status of coroutine2 to no avail, and coroutine still spits out warnings to
use coroutine2 when used. I'm not sure where in the build system things
hook in to fix this.
boost.coroutine is deprecated - but you can disable the warning (see
documentation)
boost.coroutine2 requires some C++11 features (you need to apply
cxxflags="-std=c++11" or equivalent)
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Loading...