Bug 1406903

Summary:	Consider better linking logic for lvm2 command
Product:	[Community] LVM and device-mapper	Reporter:	Zdenek Kabelac <zkabelac>
Component:	lvm2	Assignee:	LVM Team <lvm-team>
lvm2 sub component:	Compilation, building and portability	QA Contact:	cluster-qe <cluster-qe>
Status:	NEW ---	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	agk, heinzm, jbrassow, msnitzer, prajnoha, zkabelac
Version:	2.02.169	Flags:	rule-engine: lvm-technical-solution? rule-engine: lvm-test-coverage?
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:		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 Zdenek Kabelac 2016-12-21 19:15:11 UTC

Description of problem:

While lvm command links 'liblvm2cmd' as  'liblvm-internal.a'  - other users are using it as share library.

So I'd assume we should convert this 'static' usage otherwise we can't share this library code.


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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
ldd lvm links:
libdevmapper-event.so.1.02
libdevmapper.so.1.02

but NOT liblvm2cmd

ldd libdevmapper-event-lvm2.so.2.02 links:
liblvm2cmd.so.2.02
libdevmapper.so.1.02
libdevmapper-event.so.1.02

Expected results:


Additional info: