Bug 1256862 - devmapper.pc references non-existing *.pc
Summary: devmapper.pc references non-existing *.pc
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: lvm2
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: LVM and device-mapper development team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1240061
TreeView+ depends on / blocked
 
Reported: 2015-08-25 15:39 UTC by Ralf Corsepius
Modified: 2015-08-27 08:29 UTC (History)
11 users (show)

Fixed In Version: lvm2-2.02.129-1.fc24
Clone Of:
Environment:
Last Closed: 2015-08-27 08:29:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ralf Corsepius 2015-08-25 15:39:35 UTC
Description of problem:

The devmapper.pc as shipped with device-mapper-devel-1.02.105-1.fc24 is broken.

It tries to reference another *.pc file (librt.pc), which does not exist and causes calls to /usr/bin/pkg-config to fail.

Version-Release number of selected component (if applicable):
device-mapper-devel-1.02.105-1.fc24

How reproducible:
Always

Steps to Reproduce:
1. mock -r fedora-rawhide-x86_64 --init
2. mock -r fedora-rawhide-x86_64 --install \
  'pkgconfig(devmapper)' 'pkgconfig(libselinux)' 'pkgconfig(libudev)'
3. mock -r fedora-rawhide-x86_64 --shell
4. Run pkg-config inside of the chroot:
# pkg-config --cflags devmapper
Package librt was not found in the pkg-config search path.
Perhaps you should add the directory containing `librt.pc'
to the PKG_CONFIG_PATH environment variable
Package 'librt', required by 'devmapper', not found


Actual results:
cf. above

Expected results:
function.

Additional info:

- The problem here is the reference to librt in /usr/*/pkg-config/devmapper.pc:
...
Libs: -L${libdir} -ldevmapper
Requires.private: libselinux libudev librt

pkg-config expects to find a librt.pc.

This file does not exist, so pkg config errors out.

- This bug already is causing FTBFSs

Comment 1 Peter Rajnoha 2015-08-27 08:29:11 UTC
Fixed in lvm2-2.02.129-1.fc24/device-mapper-1.02.106-1.fc24.


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