Created attachment 280425 [details] emerge --info during src_compile: make[2]: Entering directory `/var/tmp/portage/app-emulation/libvirt-0.9.3/work/libvirt-0.9.3/daemon' sed \ -e 's![@]localstatedir[@]!/var!g' \ < libvirtd.qemu.logrotate.in > libvirtd.qemu.logrotate-t GEN libvirtd.lxc.logrotate sed \ -e 's![@]localstatedir[@]!/var!g' \ < libvirtd.logrotate.in > libvirtd.logrotate-t GEN libvirtd.uml.logrotate mv libvirtd.qemu.logrotate-t libvirtd.qemu.logrotate mv libvirtd.logrotate-t libvirtd.logrotate make all-am make[3]: Entering directory `/var/tmp/portage/app-emulation/libvirt-0.9.3/work/libvirt-0.9.3/daemon' CC libvirtd-libvirtd.o CC libvirtd-remote.o CC libvirtd-stream.o CC libvirtd-remote_protocol.o In file included from libvirtd.h:41:0, from stream.h:27, from stream.c:26: ../src/rpc/virnetsaslcontext.h:24:24: fatal error: sasl/sasl.h: No such file or directory compilation terminated. make[3]: *** [libvirtd-stream.o] Error 1 make[3]: *** Waiting for unfinished jobs.... In file included from libvirtd.h:41:0, from libvirtd.c:41: ../src/rpc/virnetsaslcontext.h:24:24: fatal error: sasl/sasl.h: No such file or directory compilation terminated. make[3]: *** [libvirtd-libvirtd.o] Error 1 In file included from libvirtd.h:41:0, from remote.c:33: ../src/rpc/virnetsaslcontext.h:24:24: fatal error: sasl/sasl.h: No such file or directory compilation terminated. However, I have the sasl USE flag disabled, so I think it should not be looking for sasl headers.
Have confirmed that enabling the sasl USE flag causes the ebuild to emerge successfully.
Perhaps I spoke too son wrt comment #1 I do get this postinst message: ERROR: postinst ERROR: app-emulation/libvirt-0.9.3 failed (postinst phase): python_mod_optimize(): Paths of directories / files in site-packages directories must be relative to site-packages directorties Call stack: ebuild.sh, line 56: Called pkg_postinst environment, line 2759: Called python_mod_optimize '/usr/lib64/python2.7/site-packages/libvirt.py' environment, line 4410: Called die The specific snippet of code: die "${FUNCNAME}(): Paths of directories / files in site-packages directories must be relative to site-packages directories"; But it does appear to have installed and was able to restart the libvirtd service.
Can you post the output of, emerge -pv =app-emulation/libvirt-0.9.3 please? This saves the devs time trying to figure out what USE flags actually get enabled after your profile and make.conf take effect.
I was able to reproduce the failure with USE="libvirtd -sasl", but not with both of them disabled.
(In reply to comment #3) > Can you post the output of, > > emerge -pv =app-emulation/libvirt-0.9.3 > > please? This saves the devs time trying to figure out what USE flags actually > get enabled after your profile and make.conf take effect. Yeah, sorry it was in the emerge --info: USE="libvirtd (multilib) nls python qemu udev virt-network -avahi -caps -debug -iscsi -json -lvm -lxc -macvtap -nfs -numa -openvz -parted -pcap -phyp -policykit -sasl (-selinux) -uml -virtualbox -xen"
Ah, sorry. Didn't see it in there.
@Albert, please add your full build log as attachment.
build.log coming shortly. Incidentally, unmerging the package generates a postrm error: ERROR: postrm The 'postrm' phase of the 'app-emulation/libvirt-0.9.3' package has failed with exit value 1. The problem occurred while executing the ebuild file named 'libvirt-0.9.3.ebuild' located in the '/var/db/pkg/app- emulation/libvirt-0.9.3' directory. If necessary, manually remove the environment.bz2 file and/or the ebuild file located in that directory. Removal of the environment.bz2 file is preferred since it may allow the removal phases to execute successfully. The ebuild will be sourced and the eclasses from the current portage tree will be used when necessary. Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm() removal phases to be skipped entirely. ERROR: app-emulation/libvirt-0.9.3 failed (postrm phase): python_mod_cleanup(): Paths of directories / files in site-packages directories must be relative to site-packages directories Call stack: ebuild.sh, line 56: Called pkg_postrm environment, line 2788: Called python_mod_cleanup '/usr/lib64/python2.7/site-packages/libvirt.py' environment, line 4312: Called die The specific snippet of code: die "${FUNCNAME}(): Paths of directories / files in site-packages directories must be relative to site-packages directories";
Created attachment 280441 [details] build log with USE=-sasl
Created attachment 280443 [details] build.log *with* USE=sas; Included the build.log with USE=sasl to demonstrate the postinst error message
The SASL header errors are an upstream problem. I attached the patch from https://www.redhat.com/archives/libvir-list/2011-July/msg00188.html After applying the patch, the ebuild also compiles, installs and works fine with USE="-sasl"
Created attachment 280499 [details, diff] [PATCH] Fix compilation error when SASL support is disabled
I was affected by this issue too, and I can confirm the patch from comment #12 fixed the compilation problem for me.
Fixed in 0.9.3-r1
