boost normally generates, among other sub-packages, boost-python3 and boost-python3-devel. Those latter are however missing from RHEL/CentOS 8, even with EPEL enabled:
boost-python3
boost-python3-devel
$sudo dnf search boost|grep python Last metadata expiration check: 0:45:49 ago on Sat 26 Oct 2019 07:20:14 PM CEST.
A few other Python-related sub-packages are also missing (e.g., boost-mpich-python, boost-openmpi-python).
boost-mpich-python
boost-openmpi-python
Also, note that the naming may be something like python3-boost and python3-boost-devel.
python3-boost
python3-boost-devel
The same query would show the corresponding sub-packages on RHEL/CentOS 7:
$ sudo yum search boost|grep python|grep -v i686 boost-mpich-python.x86_64 : Python run-time component of Boost.MPI library boost-openmpi-python.x86_64 : Python run-time component of Boost.MPI library boost-python.x86_64 : Run-Time component of boost python library boost-python36.x86_64 : Shared object symbolic links for Boost.Python 3 boost-python36-devel.x86_64 : Shared object symbolic links for Boost.Python 3 boost-python36-static.x86_64 : The Python3 Boost C++ static development
And it does not appear that the epel8 branch can be added to the boost source code on Pagure:
epel8
boost
$ fedpkg request-branch epel8 Could not execute request_branch: This package is already an EL package and is built on all supported arches, therefore, it cannot be in EPEL. If this is a mistake or you have an exception, please contact the Release Engineering team.
Could you deliver the missing boost sub-packages for RHEL/CentOS 8?
Thanks!
Kind regards
Denis
Cross-referenced in https://bugzilla.redhat.com/show_bug.cgi?id=1765854
The following packages are in PowerTools so I think you may be covered.
./PowerTools/x86_64/os/Packages/boost-python3-1.66.0-6.el8.i686.rpm ./PowerTools/x86_64/os/Packages/boost-build-1.66.0-6.el8.noarch.rpm ./PowerTools/x86_64/os/Packages/boost-doc-1.66.0-6.el8.noarch.rpm ./PowerTools/x86_64/os/Packages/boost-python3-devel-1.66.0-6.el8.i686.rpm ./PowerTools/x86_64/os/Packages/boost-examples-1.66.0-6.el8.noarch.rpm ./PowerTools/x86_64/os/Packages/boost-python3-devel-1.66.0-6.el8.x86_64.rpm ./PowerTools/x86_64/os/Packages/boost-graph-mpich-1.66.0-6.el8.i686.rpm ./PowerTools/x86_64/os/Packages/boost-static-1.66.0-6.el8.i686.rpm ./PowerTools/x86_64/os/Packages/boost-graph-mpich-1.66.0-6.el8.x86_64.rpm ./PowerTools/x86_64/os/Packages/boost-static-1.66.0-6.el8.x86_64.rpm ./PowerTools/x86_64/os/Packages/boost-graph-openmpi-1.66.0-6.el8.i686.rpm ./PowerTools/x86_64/os/Packages/boost-graph-openmpi-1.66.0-6.el8.x86_64.rpm ./PowerTools/x86_64/os/Packages/boost-jam-1.66.0-6.el8.x86_64.rpm ./PowerTools/x86_64/os/Packages/boost-mpich-1.66.0-6.el8.i686.rpm ./PowerTools/x86_64/os/Packages/boost-mpich-1.66.0-6.el8.x86_64.rpm ./PowerTools/x86_64/os/Packages/boost-mpich-devel-1.66.0-6.el8.i686.rpm ./PowerTools/x86_64/os/Packages/boost-mpich-devel-1.66.0-6.el8.x86_64.rpm ./PowerTools/x86_64/os/Packages/boost-mpich-python3-1.66.0-6.el8.x86_64.rpm ./PowerTools/x86_64/os/Packages/boost-numpy3-1.66.0-6.el8.i686.rpm ./PowerTools/x86_64/os/Packages/boost-numpy3-1.66.0-6.el8.x86_64.rpm ./PowerTools/x86_64/os/Packages/boost-openmpi-1.66.0-6.el8.i686.rpm ./PowerTools/x86_64/os/Packages/boost-openmpi-1.66.0-6.el8.x86_64.rpm ./PowerTools/x86_64/os/Packages/boost-openmpi-devel-1.66.0-6.el8.i686.rpm ./PowerTools/x86_64/os/Packages/boost-openmpi-devel-1.66.0-6.el8.x86_64.rpm ./PowerTools/x86_64/os/Packages/boost-python3-1.66.0-6.el8.x86_64.rpm ./PowerTools/x86_64/os/Packages/boost-openmpi-python3-1.66.0-6.el8.x86_64.rpm
Thanks Stephen, yes that's perfect!
For the record (as I may not be the only one wondering on how to get those packages):
$ sudo dnf config-manager --set-enabled PowerTools $ sudo dnf -y install boost-python3-devel boost-mpich-python3 boost-python3 boost-openmpi-python3
Would you know, by the way, how to reference (with BuildRequires) those packages from within the EPEL 8 RPM spec file?
Metadata Update from @denisarnaud: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Powertools/CRB is automatically on in the EPEL buildsystem so you should just BuildRequire them.
Login to comment on this ticket.