Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1546798

Summary:	locating devtoolset-7-dyninst shared objects
Product:	Red Hat Developer Toolset	Reporter:	Stan Cox <scox>
Component:	devtoolset-meta	Assignee:	Marek Polacek <mpolacek>
Status:	CLOSED ERRATA	QA Contact:	Martin Cermak <mcermak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	DTS 7.1 RHEL 7	CC:	jakub, kanderso, mnewsome, ohudlick
Target Milestone:	alpha
Target Release:	7.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	devtoolset-7-7.1-4.el7	Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-03 06:59:15 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 Stan Cox 2018-02-19 16:00:54 UTC

Description of problem:
As described in bug 1540169, comment 4
dyninst and devtoolset dyninst use ldconfig to find the dyninst libraries which are located in <root>/usr/lib64/dyninst
This is fine for the standard case, but for devtoolset results in two sets of dyninst libraries in the shared object cache.

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


How reproducible:


Steps to Reproduce:
1. install devtoolset-7-dyninst systemtap
2. ldd /usr/bin/stapdev
3.

Actual results:
finds /opt/rh/devtoolset-7/root/usr/lib64/dyninst/libdyninst*

Expected results:
finds /usr/lib64/dyninst/libdyninst*

Additional info:
The suggested approach is to not use ldconfig for devtoolset dyninst and to have devtoolset enable add /opt/rh/devtoolset-7/root/usr/lib64/dyninst to LD_LIBRARY_PATH so those libraries are only found when scl enable is invoked
e.g.
export LD_LIBRARY_PATH=/opt/rh/devtoolset-7/root$rpmlibdir$rpmlibdir32:/opt/rh/devtoolset-7/root$rpmlibdir/dyninst$rpmlibdir32/dyninst${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}

Comment 7 errata-xmlrpc 2018-05-03 06:59:15 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1300