Build Errors for ASIO on msvc-10.0 and -11.0

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Build Errors for ASIO on msvc-10.0 and -11.0

Boost - Dev mailing list
After seeing the announcement that library freeze is coming, I just tried
building the master snapshot with the build scripts I use for building the
windows releases. I encountered failures in msvc-10.0 and msvc-11.0 for
ASIO.

.\boost/asio/execution/any_executor.hpp(940) : error C2668:
'boost::asio::execution::detail::any_executor_base::query_fn_impl' :
ambiguous call to overloaded function
        .\boost/asio/execution/any_executor.hpp(915): could be 'void
boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void
*,const void *,const void *,boost::type *)'
        with
        [
            Ex=void,

Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &>
        ]
        .\boost/asio/execution/any_executor.hpp(902): or       'void
boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void
*,const void *,const void *,boost::type *)'
        with
        [
            Ex=void,

Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &>
        ]
        .\boost/asio/execution/any_executor.hpp(887): or       'void
boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void
*,const void *,const void *,boost::type *)'
        with
        [
            Ex=void,

Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &>
        ]
        .\boost/asio/execution/any_executor.hpp(875): or       'void
boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void
*,const void *,const void *,boost::type *)'
        with
        [
            Ex=void,

Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &>
        ]
        .\boost/asio/execution/any_executor.hpp(859): or       'void
boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void
*,const void *,const void *,boost::type *)'
        with
        [
            Ex=void,

Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &>
        ]
        .\boost/asio/execution/any_executor.hpp(849): or       'void
boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void
*,const void *,const void *,boost::type *)'
        with
        [
            Ex=void,

Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &>
        ]
        .\boost/asio/execution/any_executor.hpp(837): or       'void
boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void
*,const void *,const void *,boost::type *)'
        with
        [
            Ex=void,

Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &>
        ]
        .\boost/asio/execution/any_executor.hpp(827): or       'void
boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void
*,const void *,const void *,void *)'
        with
        [
            Ex=void,

Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &>
        ]
        while trying to match the argument list '(void *, const void *,
const void *, int)'
        .\boost/asio/execution/any_executor.hpp(1782) : see reference to
function template instantiation 'void
boost::asio::execution::detail::any_executor_base::query_fn<Ex,T1>(void
*,const void *,const void *)' being compiled
        with
        [
            Ex=void,

T1=boost::asio::execution::context_as_t<boost::asio::execution_context &>
        ]
        .\boost/asio/execution/any_executor.hpp(1782) : see reference to
function template instantiation 'const
boost::asio::execution::detail::any_executor_base::prop_fns<Poly>
*boost::asio::execution::any_executor<<unnamed-symbol>,boost::asio::execution::detail::blocking::never_t<I>,boost::asio::execution::prefer_only<InnerProperty>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0>>>::prop_fns_table<void>(void)'
being compiled
        with
        [

Poly=boost::asio::execution::any_executor<boost::asio::execution::context_as_t<boost::asio::execution_context
&>,boost::asio::execution::detail::blocking::never_t<0>,boost::asio::execution::prefer_only<boost::asio::execution::detail::blocking::possibly_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0>>>,

<unnamed-symbol>=boost::asio::execution::context_as_t<boost::asio::execution_context
&>,
            I=0,

InnerProperty=boost::asio::execution::detail::blocking::possibly_t<0>
        ]
        .\boost/asio/execution/any_executor.hpp(1782) : while compiling
class template member function
'boost::asio::execution::any_executor<<unnamed-symbol>,boost::asio::execution::detail::blocking::never_t<I>,boost::asio::execution::prefer_only<InnerProperty>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0>>>::any_executor(void)'
        with
        [

<unnamed-symbol>=boost::asio::execution::context_as_t<boost::asio::execution_context
&>,
            I=0,

InnerProperty=boost::asio::execution::detail::blocking::possibly_t<0>
        ]
        .\boost/asio/detail/io_object_impl.hpp(168) : see reference to
class template instantiation
'boost::asio::execution::any_executor<<unnamed-symbol>,boost::asio::execution::detail::blocking::never_t<I>,boost::asio::execution::prefer_only<InnerProperty>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0>>>'
being compiled
        with
        [

<unnamed-symbol>=boost::asio::execution::context_as_t<boost::asio::execution_context
&>,
            I=0,

InnerProperty=boost::asio::execution::detail::blocking::possibly_t<0>
        ]
        .\boost/asio/basic_socket.hpp(1804) : see reference to class
template instantiation
'boost::asio::detail::io_object_impl<IoObjectService,Executor>' being
compiled
        with
        [

IoObjectService=boost::asio::detail::win_iocp_socket_service<boost::asio::ip::udp>,
            Executor=boost::asio::any_io_executor
        ]
        .\boost/asio/basic_datagram_socket.hpp(53) : see reference to class
template instantiation 'boost::asio::basic_socket<Protocol,Executor>' being
compiled
        with
        [
            Protocol=boost::asio::ip::udp,
            Executor=boost::asio::any_io_executor
        ]
        libs\log\src\syslog_backend.cpp(315) : see reference to class
template instantiation 'boost::asio::basic_datagram_socket<Protocol>' being
compiled
        with
        [
            Protocol=boost::asio::ip::udp
        ]

Hopefully this can be cleared up before the beta.

Thanks,
Tom

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

Re: Build Errors for ASIO on msvc-10.0 and -11.0

Boost - Dev mailing list
On Tue, Jun 30, 2020 at 5:22 PM Tom Kent via Boost
<[hidden email]> wrote:
> I just tried building the master snapshot

You will need the new commits in develop in order to have a chance of
building, this stuff is being ironed out. Are the commits below in
this "master snapshot?"

<https://github.com/boostorg/asio/commits/develop>

If not, then you won't be able to build. While this is being worked
on, we are trying to sync Beast up with these changes so that the next
Boost release has them, as they are important for users and
discussions about networking taking place in WG21.

Thanks

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

Re: Build Errors for ASIO on msvc-10.0 and -11.0

Boost - Dev mailing list
On Tue, Jun 30, 2020 at 8:09 PM Vinnie Falco <[hidden email]> wrote:

> On Tue, Jun 30, 2020 at 5:22 PM Tom Kent via Boost
> <[hidden email]> wrote:
> > I just tried building the master snapshot
>
> You will need the new commits in develop in order to have a chance of
> building, this stuff is being ironed out. Are the commits below in
> this "master snapshot?"
>
> <https://github.com/boostorg/asio/commits/develop>
>
> If not, then you won't be able to build. While this is being worked
> on, we are trying to sync Beast up with these changes so that the next
> Boost release has them, as they are important for users and
> discussions about networking taking place in WG21.
>
>
Two days until closing for the beta, it looks like these still haven't been
merged to master? Anything we can do to move it along?

Thanks,
Tom

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

Re: Build Errors for ASIO on msvc-10.0 and -11.0

Boost - Dev mailing list
On Fri, 10 Jul 2020 at 03:30, Tom Kent via Boost <[hidden email]>
wrote:

> On Tue, Jun 30, 2020 at 8:09 PM Vinnie Falco <[hidden email]>
> wrote:
>
> > On Tue, Jun 30, 2020 at 5:22 PM Tom Kent via Boost
> > <[hidden email]> wrote:
> > > I just tried building the master snapshot
> >
> > You will need the new commits in develop in order to have a chance of
> > building, this stuff is being ironed out. Are the commits below in
> > this "master snapshot?"
> >
> > <https://github.com/boostorg/asio/commits/develop>
> >
> > If not, then you won't be able to build. While this is being worked
> > on, we are trying to sync Beast up with these changes so that the next
> > Boost release has them, as they are important for users and
> > discussions about networking taking place in WG21.
> >
> >
> Two days until closing for the beta, it looks like these still haven't been
> merged to master? Anything we can do to move it along?


Boost asio is generated from standalone asio.

PRs against boost asio don’t get any attention.

Chris does respond to issues in the root repo.

https://github.com/chriskohlhoff/asio




>
> Thanks,
> Tom
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
>
--
Richard Hodges
[hidden email]
office: +442032898513
home: +376841522
mobile: +376380212

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