[release] Boost 1.66.0 Beta 1 Release Candidate 1

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
43 messages Options
123
Reply | Threaded
Open this post in threaded view
|

[release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
The release candidates for the 1.66.0 beta release are now available at:

<https://dl.bintray.com/boostorg/beta/1.66.0.beta.1/source/>

The SHA256 checksums are as follows:

0e137e61069e95f61fe0e46aa4a5432e65e209e87d470ea3c15b0ea1327583ac
boost_1_66_0_b1_rc1.7z
eff4854c1a672830c55fd2323ebe42d5d83e0f7a3d0a9d354d8bf55289831fa0
boost_1_66_0_b1_rc1.tar.bz2
f4fb07aa1ec639707570e42a848796d9a8155f23d1ece0f0a6a0cbee99807038
boost_1_66_0_b1_rc1.tar.gz
d5f480441223f45427199697edbdd78145499084f835597247a452d2a7e1e798
boost_1_66_0_b1_rc1.zip

The in progress release notes are at:

<http://www.boost.org/users/history/in_progress.html>

And the documentation is at:

<http://www.boost.org/doc/libs/1_66_0_beta1/>

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.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
On Thu, Nov 16, 2017 at 4:39 AM, Daniel James via Boost <
[hidden email]> wrote:

> The release candidates for the 1.66.0 beta release are now available at:
>
> <https://dl.bintray.com/boostorg/beta/1.66.0.beta.1/source/>
>
> The SHA256 checksums are as follows:
>
> 0e137e61069e95f61fe0e46aa4a5432e65e209e87d470ea3c15b0ea1327583ac
> boost_1_66_0_b1_rc1.7z
> eff4854c1a672830c55fd2323ebe42d5d83e0f7a3d0a9d354d8bf55289831fa0
> boost_1_66_0_b1_rc1.tar.bz2
> f4fb07aa1ec639707570e42a848796d9a8155f23d1ece0f0a6a0cbee99807038
> boost_1_66_0_b1_rc1.tar.gz
> d5f480441223f45427199697edbdd78145499084f835597247a452d2a7e1e798
> boost_1_66_0_b1_rc1.zip
>
> The in progress release notes are at:
>
> <http://www.boost.org/users/history/in_progress.html>
>
> And the documentation is at:
>
> <http://www.boost.org/doc/libs/1_66_0_beta1/>
>
> 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'm seeing compile errors in Boost Python against msvc-11.0 (10.0 and 12.0
work!).

There are a lot of them, but they all seem to be related to this:

compile-c-c++
bin.v2\libs\python\build\msvc-11.0\release\address-model-64\link-static\threadapi-win32\threading-multi\object\life_support.obj
life_support.cpp
.\boost/python/detail/type_traits.hpp(102) : error C2143: syntax error :
missing ';' before '='
.\boost/python/detail/type_traits.hpp(102) : error C2873: 'true_' : symbol
cannot be used in a using-declaration
.\boost/python/detail/type_traits.hpp(102) : error C2513: 'int' : no
variable declared before '='
.\boost/python/detail/type_traits.hpp(103) : error C2143: syntax error :
missing ';' before '='
.\boost/python/detail/type_traits.hpp(103) : error C2873: 'false_' : symbol
cannot be used in a using-declaration
.\boost/python/detail/type_traits.hpp(103) : error C2513: 'int' : no
variable declared before '='

    call
"C:\Users\tomkent\AppData\Local\Temp\2\b2_msvc_11.0_vcvarsall_amd64.cmd"
>nul
cl /Zm800 -nologo
@"bin.v2\libs\python\build\msvc-11.0\release\address-model-64\link-static\threadapi-win32\threading-multi\object\life_support.obj.rsp"

...failed compile-c-c++
bin.v2\libs\python\build\msvc-11.0\release\address-model-64\link-static\threadapi-win32\threading-multi\object\life_support.obj...


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      FAIL
msvc-11.0   64      FAIL
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
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.


The full build log can be found here:
https://gist.github.com/teeks99/3a8026b06cd53ef2746a4e08bff1a026

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
Hi Tom,

thanks for raising this issue.

On 16.11.2017 09:36, Tom Kent via Boost wrote:

> On Thu, Nov 16, 2017 at 4:39 AM, Daniel James via Boost <
> [hidden email]> wrote:
>
>> The release candidates for the 1.66.0 beta release are now available at:
>>
>> <https://dl.bintray.com/boostorg/beta/1.66.0.beta.1/source/>
>>
>> The SHA256 checksums are as follows:
>>
>> 0e137e61069e95f61fe0e46aa4a5432e65e209e87d470ea3c15b0ea1327583ac
>> boost_1_66_0_b1_rc1.7z
>> eff4854c1a672830c55fd2323ebe42d5d83e0f7a3d0a9d354d8bf55289831fa0
>> boost_1_66_0_b1_rc1.tar.bz2
>> f4fb07aa1ec639707570e42a848796d9a8155f23d1ece0f0a6a0cbee99807038
>> boost_1_66_0_b1_rc1.tar.gz
>> d5f480441223f45427199697edbdd78145499084f835597247a452d2a7e1e798
>> boost_1_66_0_b1_rc1.zip
>>
>> The in progress release notes are at:
>>
>> <http://www.boost.org/users/history/in_progress.html>
>>
>> And the documentation is at:
>>
>> <http://www.boost.org/doc/libs/1_66_0_beta1/>
>>
>> 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'm seeing compile errors in Boost Python against msvc-11.0 (10.0 and 12.0
> work!).
>
> There are a lot of them, but they all seem to be related to this:
>
> compile-c-c++
> bin.v2\libs\python\build\msvc-11.0\release\address-model-64\link-static\threadapi-win32\threading-multi\object\life_support.obj
> life_support.cpp
> .\boost/python/detail/type_traits.hpp(102) : error C2143: syntax error :
> missing ';' before '='
> .\boost/python/detail/type_traits.hpp(102) : error C2873: 'true_' : symbol
> cannot be used in a using-declaration
> .\boost/python/detail/type_traits.hpp(102) : error C2513: 'int' : no
> variable declared before '='
> .\boost/python/detail/type_traits.hpp(103) : error C2143: syntax error :
> missing ';' before '='
> .\boost/python/detail/type_traits.hpp(103) : error C2873: 'false_' : symbol
> cannot be used in a using-declaration
> .\boost/python/detail/type_traits.hpp(103) : error C2513: 'int' : no
> variable declared before '='

It looks like we falsely assume the compiler understands C++11 and thus
use attempt to use std::integral_constant. Could it be that the
conditional in
https://github.com/boostorg/python/blob/develop/include/boost/python/detail/type_traits.hpp#L10-L11
is wrong ? (If it was set to 'true' for MSVC 10.0, and 'false' for MSVC
>= 11.0 , when it should in fact be 'true' for MSVC 11.0, too, this
might explain the error. But given that I'm not very familiar with MSVC,
this is pure speculation. I'd appreciate any help from some Windows
experts.)

Thanks,

Stefan

--

      ...ich hab' noch einen Koffer in Berlin...
   


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
Stefan Seefeld wrote:
> It looks like we falsely assume the compiler understands C++11 and thus
> use attempt to use std::integral_constant. Could it be that the
> conditional in
> https://github.com/boostorg/python/blob/develop/include/boost/python/detail/type_traits.hpp#L10-L11 
> is wrong ?

You should probably be checking BOOST_NO_CXX11_HDR_TYPE_TRAITS there unless
you have a specific reason not to do so.


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
On 16 November 2017 at 15:10, Peter Dimov via Boost
<[hidden email]> wrote:

> Stefan Seefeld wrote:
>>
>> It looks like we falsely assume the compiler understands C++11 and thus
>> use attempt to use std::integral_constant. Could it be that the conditional
>> in
>> https://github.com/boostorg/python/blob/develop/include/boost/python/detail/type_traits.hpp#L10-L11
>> is wrong ?
>
>
> You should probably be checking BOOST_NO_CXX11_HDR_TYPE_TRAITS there unless
> you have a specific reason not to do so.

Yes, but I think the error is because it doesn't understand the C++11
type alias. Better to use:

typedef std::integral_constant<bool, true> true_;
typedef std::integral_constant<bool, false> false_;

According to MSDN, std::integral_constant was in Visual Studio 2008,
which is Visual C++ 9.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On Thu, Nov 16, 2017 at 11:39 AM, Daniel James via Boost
<[hidden email]> 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.

PS C:\vc\boost> .\bootstrap.bat
Building Boost.Build engine

Failed to build Boost.Build engine.
Please consult bootstrap.log for further diagnostics.

You can try to obtain a prebuilt binary from

   http://sf.net/project/showfiles.php?group_id=7586&package_id=72941

Also, you can file an issue at http://svn.boost.org
Please attach bootstrap.log in that case.

**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.4.3
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x86'
###
### Using 'vc141' toolset.
###

C:\Users\Olaf\source>if exist bootstrap rd /S /Q bootstrap

C:\Users\Olaf\source>md bootstrap

C:\Users\Olaf\source>cl /nologo /RTC1 /Zi /MTd /Fobootstrap/
/Fdbootstrap/ -DNT -DYYDEBUG -wd4996 kernel32.lib advapi32.lib
user32.lib /Febootstrap\yyacc0 yyacc.c
yyacc.c
c1: fatal error C1083: Cannot open source file: 'yyacc.c': No such
file or directory





--
Olaf

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On Thu, Nov 16, 2017 at 11:39 AM, Daniel James via Boost
<[hidden email]> 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.

MSVC 15.5.0 preview 4:

1>Info: Boost.Config is older than your compiler version - probably
nothing bad will happen - but you may wish to look for an update Boost
version.  Define BOOST_CONFIG_SUPPRESS_OUTDATED_MESSAGE to suppress
this message.
1>c:\vc\boost\boost\asio\detail\type_traits.hpp(57): error C4996:
'std::result_of': warning STL4014: std::result_of and std::result_of_t
are deprecated in C++17. They are superseded by std::invoke_result and
std::invoke_result_t. You can define
_SILENCE_CXX17_RESULT_OF_DEPRECATION_WARNING or
_SILENCE_ALL_CXX17_DEPRECATION_WARNINGS to acknowledge that you have
received this warning.

1>c:\program files (x86)\microsoft visual
studio\preview\community\vc\tools\msvc\14.12.25827\include\type_traits(1807):
note: see declaration of 'std::result_of'
1>c:\vc\boost\boost\asio\associated_allocator.hpp(103): error C4996:
'std::allocator<void>': warning STL4009: std::allocator<void> is
deprecated in C++17. You can define
_SILENCE_CXX17_ALLOCATOR_VOID_DEPRECATION_WARNING or
_SILENCE_ALL_CXX17_DEPRECATION_WARNINGS to acknowledge that you have
received this warning.

1>c:\program files (x86)\microsoft visual
studio\preview\community\vc\tools\msvc\14.12.25827\include\xmemory0(1087):
note: see declaration of 'std::allocator<void>'
1>c:\vc\boost\boost\asio\use_future.hpp(130): error C4996:
'std::allocator<void>': warning STL4009: std::allocator<void> is
deprecated in C++17. You can define
_SILENCE_CXX17_ALLOCATOR_VOID_DEPRECATION_WARNING or
_SILENCE_ALL_CXX17_DEPRECATION_WARNINGS to acknowledge that you have
received this warning.

1>c:\program files (x86)\microsoft visual
studio\preview\community\vc\tools\msvc\14.12.25827\include\xmemory0(1087):
note: see declaration of 'std::allocator<void>'
1>Done building project "Polylines.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========



--
Olaf

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
> -----Original Message-----
> From: Boost [mailto:[hidden email]] On Behalf Of Daniel
> James via Boost
> Sent: Donnerstag, 16. November 2017 11:39
> To: [hidden email]
> Cc: Daniel James <[hidden email]>
> Subject: [boost] [release] Boost 1.66.0 Beta 1 Release Candidate 1
>
> The release candidates for the 1.66.0 beta release are now available at:
>  [...]
>
> 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.

A first smoke test building one big project worked fine for me with VS 15.4.4.
Only the annoying errors because I forgot to delete %TEMP%\ b2_msvc_*.cmd again:
https://github.com/boostorg/build/issues/257

Marcel


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
On Thu, Nov 16, 2017 at 4:55 PM, Marcel Raad via Boost
<[hidden email]> wrote:
> A first smoke test building one big project worked fine for me with VS 15.4.4.

Has 15.4.4 been released yet?
--
Olaf

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
> -----Original Message-----
> From: Olaf van der Spek [mailto:[hidden email]]
> Sent: Donnerstag, 16. November 2017 17:06
> To: [hidden email]
> Cc: Marcel Raad <[hidden email]>
> Subject: Re: [boost] [release] Boost 1.66.0 Beta 1 Release Candidate 1
>
> On Thu, Nov 16, 2017 at 4:55 PM, Marcel Raad via Boost
> <[hidden email]> wrote:
> > A first smoke test building one big project worked fine for me with VS
> 15.4.4.
>
> Has 15.4.4 been released yet?

Yes, I updated yesterday morning.

Marcel


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On 16.11.2017 10:21, Daniel James via Boost wrote:

> On 16 November 2017 at 15:10, Peter Dimov via Boost
> <[hidden email]> wrote:
>> Stefan Seefeld wrote:
>>> It looks like we falsely assume the compiler understands C++11 and thus
>>> use attempt to use std::integral_constant. Could it be that the conditional
>>> in
>>> https://github.com/boostorg/python/blob/develop/include/boost/python/detail/type_traits.hpp#L10-L11
>>> is wrong ?
>>
>> You should probably be checking BOOST_NO_CXX11_HDR_TYPE_TRAITS there unless
>> you have a specific reason not to do so.
> Yes, but I think the error is because it doesn't understand the C++11
> type alias. Better to use:
>
> typedef std::integral_constant<bool, true> true_;
> typedef std::integral_constant<bool, false> false_;
>
> According to MSDN, std::integral_constant was in Visual Studio 2008,
> which is Visual C++ 9.

OK, thanks. I have committed
https://github.com/boostorg/python/commit/b9d0d974995d2ed6a7aeed877ee4d8ab0a5b26cf
and will merge to master once the change cycles through a round of
tests. (I have to admit that I find it extremely daunting to navigate
the online test matrix. There are so many false positives that it's hard
to spot actual failures.)

Regards,

Stefan

--

      ...ich hab' noch einen Koffer in Berlin...
   


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
On 16 November 2017 at 16:16, Stefan Seefeld via Boost
<[hidden email]> wrote:
>
> OK, thanks. I have committed
> https://github.com/boostorg/python/commit/b9d0d974995d2ed6a7aeed877ee4d8ab0a5b26cf
> and will merge to master once the change cycles through a round of
> tests. (I have to admit that I find it extremely daunting to navigate
> the online test matrix. There are so many false positives that it's hard
> to spot actual failures.)

Presumably a lot of those are due to python not being available or
properly set up, would it be possible to detect this in boost build?

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
On 16.11.2017 11:33, Daniel James via Boost wrote:

> On 16 November 2017 at 16:16, Stefan Seefeld via Boost
> <[hidden email]> wrote:
>> OK, thanks. I have committed
>> https://github.com/boostorg/python/commit/b9d0d974995d2ed6a7aeed877ee4d8ab0a5b26cf
>> and will merge to master once the change cycles through a round of
>> tests. (I have to admit that I find it extremely daunting to navigate
>> the online test matrix. There are so many false positives that it's hard
>> to spot actual failures.)
> Presumably a lot of those are due to python not being available or
> properly set up, would it be possible to detect this in boost build?

Of course !
I agree, such situations should be flagged much earlier, and the
Boost.Python build (and tests) skipped. Sometime however the failure is
different, though, but with the same net effect: rendering the test
results useless as the failures don't tell anything about the code, but
rather the testing platform setup.


Stefan

--

      ...ich hab' noch einen Koffer in Berlin...
   


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
This is Microsoft's bug, they should not change current directory in
their vsdevcmd_end.bat.

https://github.com/boostorg/build/pull/252


On Thu, Nov 16, 2017 at 6:26 PM, Olaf van der Spek via Boost
<[hidden email]> wrote:

> On Thu, Nov 16, 2017 at 11:39 AM, Daniel James via Boost
> <[hidden email]> 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.
>
> PS C:\vc\boost> .\bootstrap.bat
> Building Boost.Build engine
>
> Failed to build Boost.Build engine.
> Please consult bootstrap.log for further diagnostics.
>
> You can try to obtain a prebuilt binary from
>
>    http://sf.net/project/showfiles.php?group_id=7586&package_id=72941
>
> Also, you can file an issue at http://svn.boost.org
> Please attach bootstrap.log in that case.
>
> **********************************************************************
> ** Visual Studio 2017 Developer Command Prompt v15.4.3
> ** Copyright (c) 2017 Microsoft Corporation
> **********************************************************************
> [vcvarsall.bat] Environment initialized for: 'x86'
> ###
> ### Using 'vc141' toolset.
> ###
>
> C:\Users\Olaf\source>if exist bootstrap rd /S /Q bootstrap
>
> C:\Users\Olaf\source>md bootstrap
>
> C:\Users\Olaf\source>cl /nologo /RTC1 /Zi /MTd /Fobootstrap/
> /Fdbootstrap/ -DNT -DYYDEBUG -wd4996 kernel32.lib advapi32.lib
> user32.lib /Febootstrap\yyacc0 yyacc.c
> yyacc.c
> c1: fatal error C1083: Cannot open source file: 'yyacc.c': No such
> file or directory
>
>
>
>
>
> --
> Olaf
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
> -----Original Message-----
> From: Boost [mailto:[hidden email]] On Behalf Of Marcel
> Raad via Boost
> Sent: Donnerstag, 16. November 2017 16:55
> To: [hidden email]
> Cc: Marcel Raad <[hidden email]>
> Subject: Re: [boost] [release] Boost 1.66.0 Beta 1 Release Candidate 1
>
> A first smoke test building one big project worked fine for me with VS 15.4.4.

This project obviously didn't use Asio. There are breaking changes in the "Initial merge of Networking TS compatibility." commit, which should probably at least be mentioned in Asio's changelog? The changelog is older than that commit, unfortunately.

Also, ScopeExit still doesn't work with MSVC's /permissive- (ISO C++ compatibility mode), for which there is a PR:
https://github.com/boostorg/scope_exit/pull/3

Marcel

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
On Thu, Nov 16, 2017 at 1:42 PM, Marcel Raad via Boost
<[hidden email]> wrote:
> There are breaking changes in the "Initial merge of Networking TS compatibility." commit

I updated Beast to use the "Net.TS-flavored Boost.Asio" (my name for
the new Boost.Asio implementation) do you have any specific questions
about the changes that I might be able to answer?

Thanks

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
Hi Vinnie,

> -----Original Message-----
> From: Boost [mailto:[hidden email]] On Behalf Of Vinnie
> Falco via Boost
> Sent: Donnerstag, 16. November 2017 23:04
> To: [hidden email]
> Cc: Vinnie Falco <[hidden email]>
> Subject: Re: [boost] [release] Boost 1.66.0 Beta 1 Release Candidate 1
>
> On Thu, Nov 16, 2017 at 1:42 PM, Marcel Raad via Boost
> <[hidden email]> wrote:
> > There are breaking changes in the "Initial merge of Networking TS
> compatibility." commit
>
> I updated Beast to use the "Net.TS-flavored Boost.Asio" (my name for
> the new Boost.Asio implementation) do you have any specific questions
> about the changes that I might be able to answer?

thanks for the offer! All issues are sorted out now:
- we were still using the deprecated asio::strand typedef as there were no warnings
- we were reyling on implicit io_service.hpp includes
- strand::wrap lost support for more than two function arguments as detail::binder[3..5] were removed. Chris Kohlhoff just responded to me privately that he'll add them back.

Thanks,
Marcel


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On 16 November 2017 at 18:23, Mikhail Strelnikov via Boost
<[hidden email]> wrote:
> This is Microsoft's bug, they should not change current directory in
> their vsdevcmd_end.bat.
>
> https://github.com/boostorg/build/pull/252

It looks like there's an incoming workaround:

https://github.com/boostorg/build/pull/263

I'd rather not delay this beta for this, as it's an issue with a
preview compiler, but hopefully it should be fixed soon.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On 16 November 2017 at 22:03, Vinnie Falco via Boost
<[hidden email]> wrote:
> On Thu, Nov 16, 2017 at 1:42 PM, Marcel Raad via Boost
> <[hidden email]> wrote:
>> There are breaking changes in the "Initial merge of Networking TS compatibility." commit
>
> I updated Beast to use the "Net.TS-flavored Boost.Asio" (my name for
> the new Boost.Asio implementation) do you have any specific questions
> about the changes that I might be able to answer?

It's be useful if someone wrote some release notes. It doesn't have to
be the maintainer.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.66.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On Fri, Nov 17, 2017 at 10:30 AM, Daniel James via Boost
<[hidden email]> wrote:

> On 16 November 2017 at 18:23, Mikhail Strelnikov via Boost
> <[hidden email]> wrote:
>> This is Microsoft's bug, they should not change current directory in
>> their vsdevcmd_end.bat.
>>
>> https://github.com/boostorg/build/pull/252
>
> It looks like there's an incoming workaround:
>
> https://github.com/boostorg/build/pull/263
>
> I'd rather not delay this beta for this, as it's an issue with a
> preview compiler, but hopefully it should be fixed soon.

15.4 is not preview..


--
Olaf

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
123