DescriptionRichard W.M. Jones
2014-08-27 14:19:53 UTC
Description of problem:
$ pkg-config --libs libvirt
-lvirt -ldl -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic
obviously only -lvirt and possibly -ldl should be there.
Version-Release number of selected component (if applicable):
libvirt-1.1.3.5-2.fc20.x86_64
Additional info:
Upstream fix is
commit 1167751fcb949b44eddf3d0bfed5473e13c7e94a
Author: Daniel P. Berrange <berrange>
Date: Fri Jun 20 17:45:05 2014 +0100
Don't include @LIBS@ in libvirt.pc.in file
The libvirt.pc file we install is ending up polluted with a
load of compiler flags that should be private to the libvirt
build. eg
Libs: -L${libdir} -lvirt -ldl -O2 -g -pipe -Wall \
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions \
-fstack-protector-strong --param=ssp-buffer-size=4 \
-grecord-gcc-switches -m64 -mtune=generic
this is caused by including @LIBS@ in the Libs: line of the
pkgconfig.pc.in file.
Next build for Fedora will be fixed; this is on the v1.1.3-maint branch now
commit 76ad3133fae206f6ccb3f3c0528c2ec6bd6b62bb
Author: Daniel P. Berrange <berrange>
Date: Fri Jun 20 17:45:05 2014 +0100
Don't include @LIBS@ in libvirt.pc.in file
...
(cherry picked from commit 1167751fcb949b44eddf3d0bfed5473e13c7e94a)
Comment 2Fedora Update System
2014-09-14 19:00:34 UTC