Created attachment 363356 [details] build.log I originally hijacked a security bug to report this but since this seems to be a real issue I'm going to properly report it as it's own bug. build.log says it all.
Well firstly we'll remove 1.1.1-r5 from the title since its no longer in the tree. What's your emerge --info? You've got something somewhere tweaked slightly. libvirt only works with the Linux rpcgen and not any other platform's (e.g. FreeBSD, Mac OS X) and the error you're getting is the error you would see when you're working with the non-native rpcgen. I'm not seeing this and you're honestly the first to report it which is why I'm wondering what's different about your system.
I'm building in catalyst under grsec as mentioned in the bug from "see also". I'll modify catalyst to emit an emerge --info on failure (takes a few seconds) but getting back to the error will take a few. please stand by.
So basically it works when I build in catalyst as long as I don't build it during the kernel callback. I'm sure there is some arcane issue with the way it builds in a minimal chroot which is likely missing something blah blah blah. It doens't need a compiled kernel to build so building it as a kernel callback is wrong anyway.
(In reply to Rick Farina (Zero_Chaos) from comment #3) > So basically it works when I build in catalyst as long as I don't build it > during the kernel callback. I'm sure there is some arcane issue with the > way it builds in a minimal chroot which is likely missing something blah > blah blah. It doens't need a compiled kernel to build so building it as a > kernel callback is wrong anyway. ugh. Yeah this points to magic. I know that there's some magic and hand waving that libvirt does with rpcgen, which is why it only works on Linux. I've been meaning to dig into what its doing and try to clean it up to be a little more portable. So hopefully in the future you won't have any restrictions on how you want to build it.
(In reply to Doug Goldstein from comment #4) > ugh. Yeah this points to magic. I know that there's some magic and hand > waving that libvirt does with rpcgen, which is why it only works on Linux. > I've been meaning to dig into what its doing and try to clean it up to be a > little more portable. So hopefully in the future you won't have any > restrictions on how you want to build it. Honestly this could easily be something missing from the kerncache chroot and be totally genkernel's fault, I have no clue. I wouldn't spin a lot of effort on it, only things which hard require a compiled kernel should be build like that.