1406903 – Consider better linking logic for lvm2 command

Bug 1406903 - Consider better linking logic for lvm2 command

Summary: Consider better linking logic for lvm2 command

Keywords:
Status:	NEW
Alias:	None
Product:	LVM and device-mapper
Classification:	Community
Component:	lvm2
Sub Component:
Version:	2.02.169
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	---
Target Release:	---
Assignee:	LVM Team
QA Contact:	cluster-qe
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2016-12-21 19:15 UTC by Zdenek Kabelac
Modified:	2023-08-10 15:39 UTC (History)
CC List:	6 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:
Flags:	rule-engine: lvm-technical-solution? rule-engine: lvm-test-coverage?

Attachments	(Terms of Use)

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:

Note You need to log in before you can comment on or make changes to this bug.