Bug 1727305

Summary:	boost_python3-devel doesn't provide libboost_python3.so
Product:	[Fedora] Fedora	Reporter:	Andreas Schneider <asn>
Component:	boost	Assignee:	Jonathan Wakely <jwakely>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	andrea.manzi, asn, dakingun, denis.arnaud_fedora, jwakely
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-09 09:00:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andreas Schneider 2019-07-05 13:32:36 UTC

Description of problem:

The boost_python3-devel package doesn't provide libboost_python3.so. So projects which just try to link with -lboost_python3 fail.

Example py3exiv2.

Comment 1 Andrea 2019-07-08 19:13:58 UTC

Hi,
i'm maitaining the boost-python3 package on EPEL7 only.
Do you see this issue there?

cause from what i see the package ( boost-python36-devel), contains the .so file

rpm -ql boost-python36-devel

/usr/lib64/libboost_python3-mt.so
/usr/lib64/libboost_python3.so
/usr/share/licenses/boost-python36-devel-1.53.0
/usr/share/licenses/boost-python36-devel-1.53.0/LICENSE_1_0.txt

Comment 2 Andreas Schneider 2019-07-09 07:48:37 UTC

This is about rawhide and Fedora 30 :-)

Comment 3 Jonathan Wakely 2019-07-09 09:00:35 UTC

This is not a bug, the library is called libboost_python37.so now, so you need to fix packages that assume it's called libboost_python3.so.

This was an upstream change, see the Boost 1.67.0 release notes:

"The library name now includes the version suffix of the Python version used to compile it. For example, a variant compiled with Python 2.7 will produce library names boost_python27 and boost_numpy27, etc.. Combined with a related fix in Boost.Build, this means that it is now possible to build variants for multiple Python versions in a single build process."

In an RPM spec file you should link to libboost_python%{python3_version_nodots}.so as the current version in the Fedora release, e.g. by linking with -lboost_python%{python3_version_nodots}