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
uhd host libs fail to build with boost >= 1.87.0 (1.86 is ok) due to the removal of previously deprecated functions
Setup Details
OpenMandriva Lx Cooker or any other OS with boost 1.87.0 or higher
Expected Behavior
compiles
Actual Behaviour
fails to compile
Steps to reproduce the problem
Update to boost 1.87.0
Try to build uhd
Additional Information
Here's a partial patch that fixes the obvious issues that have a straight forward replacement. uhd-boost-1.87.0.patch.txt
It's not a complete fix though, after fixing these issues it gets to another problem.
/home/bero/abf/uhd/BUILD/uhd-4.7.0.0-build/uhd-4.7.0.0/host/lib/deps/rpclib/lib/rpc/client.cc:159:18: error: no matching member function for call to 'resolve'
159 | resolver.resolve({pimpl->addr_, std::to_string(pimpl->port_)});
| ~~~~~~~~~^~~~~~~
and
/home/bero/abf/uhd/BUILD/uhd-4.7.0.0-build/uhd-4.7.0.0/host/lib/deps/rpclib/lib/rpc/client.cc:44:21: error: no type named 'iterator' in 'boost::asio::ip::basic_resolver<boost::asio::ip::tcp>'; did you mean 'std::_Bit_const_iterator::iterator'?
44 | void do_connect(tcp::resolver::iterator endpoint_iterator) {
| ^~~~~~~~~~~~~~~~~~~~~~~
| std::_Bit_const_iterator::iterator
Not sure how to fix those right now.
The text was updated successfully, but these errors were encountered:
Issue Description
uhd host libs fail to build with boost >= 1.87.0 (1.86 is ok) due to the removal of previously deprecated functions
Setup Details
OpenMandriva Lx Cooker or any other OS with boost 1.87.0 or higher
Expected Behavior
compiles
Actual Behaviour
fails to compile
Steps to reproduce the problem
Additional Information
Here's a partial patch that fixes the obvious issues that have a straight forward replacement.
uhd-boost-1.87.0.patch.txt
It's not a complete fix though, after fixing these issues it gets to another problem.
and
Not sure how to fix those right now.
The text was updated successfully, but these errors were encountered: