Bug 1300664

Summary: bad soname in libpapi
Product: Red Hat Enterprise Linux 6 Reporter: Dave Love <dave.love>
Component: papiAssignee: William Cohen <wcohen>
Status: CLOSED WONTFIX QA Contact: qe-baseos-tools-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.7CC: ohudlick
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-21 14:14:12 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 Dave Love 2016-01-21 11:42:51 UTC
Description of problem:

The soname of libpapi is libpapi.so (without a version number).  That's obviously wrong, but it specifically breaks anything using it if you have another version of papi installed (in my case as an SCL), e.g. for Lustre support (#1262015).

$ readelf -d /usr/lib64/libpapi.so* | grep SONAME
 0x000000000000000e (SONAME)             Library soname: [libpapi.so]
 0x000000000000000e (SONAME)             Library soname: [libpapi.so]
 0x000000000000000e (SONAME)             Library soname: [libpapi.so]

Version-Release number of selected component (if applicable):

papi-5.1.1-11.el6.x86_64

Comment 2 William Cohen 2016-01-21 14:14:12 UTC
The lack of so version for the older papi library is not ideal. Changing it to be versioned may break existing code customer code already linked with this particular library, so versioning it is not really an option.

You should take a look at how the RHEL-6 pcp srpm package is built to use access an alternative version papi libraries. It uses the papi-5.1.1 libraries on RHEL-6 without issue.