You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Build fails with upcoming Boost 1.87.0 (tested beta1, stable release probably in December) due to Boost Asio removal of some deprecated APIs boostorg/asio@a69e0e1.
/tmp/osrm-backend-20241119-79427-bkjo50/include/server/server.hpp:56:46: error: expected ';' after expression
56 | boost::asio::ip::tcp::resolver::query query(address, port_string);
| ^
| ;
/tmp/osrm-backend-20241119-79427-bkjo50/include/server/server.hpp:56:9: error: no member named 'query' in 'boost::asio::ip::basic_resolver<boost::asio::ip::tcp>'; did you mean 'boost_asio_query_fn::query'?
56 | boost::asio::ip::tcp::resolver::query query(address, port_string);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| boost_asio_query_fn::query
This has been deprecated since Boost 1.66.0 boostorg/asio@b60e92b. Looking at Boost commit, something like following may work:
@@ -53,8 +53,7 @@ class Server
const auto port_string = std::to_string(port);
boost::asio::ip::tcp::resolver resolver(io_context);
- boost::asio::ip::tcp::resolver::query query(address, port_string);- boost::asio::ip::tcp::endpoint endpoint = *resolver.resolve(query);+ boost::asio::ip::tcp::endpoint endpoint = *resolver.resolve(address, port_string).begin();
acceptor.open(endpoint.protocol());
#ifdef SO_REUSEPORT
Steps to reproduce
Please provide the steps required to reproduce your problem.
Issue
Build fails with upcoming Boost 1.87.0 (tested beta1, stable release probably in December) due to Boost Asio removal of some deprecated APIs boostorg/asio@a69e0e1.
This has been deprecated since Boost 1.66.0 boostorg/asio@b60e92b. Looking at Boost commit, something like following may work:
Steps to reproduce
Please provide the steps required to reproduce your problem.
osrm-backend
, eithermaster
branch or 5.27.1.Specifications
Please provide details of your development environment.
The text was updated successfully, but these errors were encountered: