Hey all,
I'm back with another question about patching a package for the Focal
release. My concern is about Boost 1.71, which now ships its own native
CMake config. Previously, FindBoost.cmake was a module supplied by
cmake-data, but now the one from Boost itself takes precedence (as it
should).
Unfortunately, the switchover has meant a change in behaviour for code that
was previously using Boost with Python 3. In Bionic, if you wanted the
Boost Python 3 bindings, you did:
find_package(Boost COMPONENTS python3)
But now, in Focal, this is broken and you have to do one of these two:
find_package(Boost COMPONENTS python38)
find_package(Boost COMPONENTS python)
Neither of which would have worked to get you Python 3 bindings in Bionic—
the first would have just failed (the component name to use was
"python3-py35", now unsupported), and the second would have got you Python
2 bindings. I took this up with the upsteam maintainer and they have
patched Boost to support the python3 component, but the change won't land
until Boost 1.73 is released:
https://github.com/boostorg/boost_install/issues/31
I've also filed a ticket against boost1.71 on launchpad:
https://bugs.launchpad.net/ubuntu/+source/boost1.71/+bug/1865209
What is the best path forward to getting Ubuntu Focal's Boost 1.71 version
patched so that the python3 component continues to work into Focal? As
there have already been several Ubuntu-specific patch releases (authors
cc'd), it doesn't seem like it makes sense to go back to Debian with this
one.
Thanks for any thoughts.
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
