Created attachment 389790 [details]
This does not result in build failure, but likely make it impossible to enable firewalld support.
build log is truncated and contains only configure phase. Relevant part:
checking for gnutls/crypto.h... yes
checking for pkcheck... /usr/bin/pkcheck
checking whether pkcheck supports uid value... yes
./configure: 63906: test: xno: unexpected operator
checking for dtrace... no
checking for mntent.h... (cached) yes
checking for mount... /bin/mount
Wow. Upstream already commited the fix:
Will be in the next release.
Thanks for the info. This is now fixed in versions 220.127.116.11 and 1.2.10 in the tree and will be phased out with a stabilization of one of those two versions.
*libvirt-18.104.22.168-r1 (20 Nov 2014)
20 Nov 2014; Matthias Maier <email@example.com>
+libvirt-22.214.171.124-r1.ebuild, -libvirt-126.96.36.199.ebuild, libvirt-1.2.10.ebuild:
fix firewalld configuration wrt bug #529898
Just one question: Why have you marked this bug as a blocker of bug 526268 ? I can configure just fine with sh -> dash. If this doesn't work for you, please file a separate bug report instead.
(In reply to Matthias Maier from comment #2)
To reproduce this bug you need either dash with LINENO support (=app-shells/dash-0.5.8.1) or set env variable CONFIG_SHELL=/bin/dash. Actually many blockers of bug 526268 (most if not all of the bugs filed by Diego) can only be reproduced when the same conditions are met.
Ah, no. I'm sorry I completely missed the fact that above configure error only happens with app-shells/dash.
I'm sorry - I was confused. I tested with dash (I have it set as default sh) but only _after_ I already applied the patch (and haven't seen a configuration error for obvious reasons).
It would have helped if the "bashism" weren't removed from the summary or if the summary had contained a "with app-shells/dash". :-P
Anyway. Patch applied.
Resolved along with the usual, monthly security stabilization :-]