If looks as if mit-krb5's "make install" (rather than the ebuild) changes to ownership of "${ED}/usr/bin/ksu" to "root", which succeeds. However, portage then bombs out when completing the "qmerge"/"src_install" step, leaving the package in a semi-installed state with files on the filesystem but not recorded as being installed. This looks as if it will affect all (prefix) installs where the portage user isn't root.
well, why does the chown root succeed in the first place?
Heh - good point, I'd not noticed that... on Linux you can't give files away. IRIX is perfectly happy for you to change the ownership on any file you own (including to be owned by root) - but then, of course, you can't take it back again. If turns out that IRIX has a "restricted_chown" systune variable which will prevent users from changing the ownership of their files to other users, but this is a system-wide setting which is not enabled by default. I'd be a little reluctant to activate it without looking into it further unless anything breaks. In any case, we're still talking about a failure - just at a different point, yes? (I'd hoped that setting "CHOWNPROG=true" in the ebuild would get around this problem, but either it doesn't or I'm setting it (in "src_install") too late...)
you should pass it onto the emake call, not export it in the environment. You can't set restricted_chown or similar for a session? The makefile may just ignore the error if chown fails. Anyway, removing that or disabling it is fine with me.
Unfortunately, restricted_chown is a kernel tunable, as it affects the (global) operation of the *chown() calls. I'll see if passing the variable to emake works any better...
We are sorry to close this bug. We lack the man-power and devotion to support mips-irix in the tree.