Bug 1470730 - pkg-config --cflags libinput , output now includes -I/usr/include/
Summary: pkg-config --cflags libinput , output now includes -I/usr/include/
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: meson
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Igor Gnatenko
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-13 14:19 UTC by Rex Dieter
Modified: 2017-07-13 21:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-13 21:57:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Rex Dieter 2017-07-13 14:19:55 UTC
summary says it all,
pkg-config --cflags libinput
recently began to output
-I/usr/include/
which causes problems elsewhere

Normally, pkg-config filters out -I/usr/include, but libinput includes a trailing slash recently.

Compare f25's libinput.pc:

-----
prefix=/usr
exec_prefix=/usr
datarootdir=${prefix}/share
pkgdatadir=/usr/share/libinput
libdir=/usr/lib64
includedir=/usr/include

Name: Libinput
Description: Input device library
Version: 1.6.3
Cflags: -I${includedir}
Libs: -L${libdir} -linput
Libs.private: -lm -lrt
Requires.private: libudev
----

with rawhide's:
----
prefix=/usr
libdir=${prefix}/lib64
includedir=${prefix}/include

Name: Libinput
Description: Input device library
Version: 1.8.0
Libs: -L${libdir} -linput
Cflags: -I${includedir}/
----

Comment 1 Rex Dieter 2017-07-13 14:20:56 UTC
Apparently meson issue?

https://github.com/mesonbuild/meson/issues/2050

Comment 2 Rex Dieter 2017-07-13 14:22:59 UTC
For full disclosure, the inclusion of -I/usr/include cflags is a cause for qt5-qtbase build failures (gory internals of using c++ and converting some system includes from -I to -isystem)

Comment 3 Igor Gnatenko 2017-07-13 21:57:46 UTC
I backported patch and rebuilt libinput, hopefully should be fixed.


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