Emerge fails due to the error provided in the txt file (patch fails). This happens with both available versions. Reproducible: Always Steps to Reproduce: 1.emerge netkit-rsh
Created attachment 169496 [details] Error from the Emerge
Created attachment 169498 [details] Patch Output
Created attachment 169500 [details] Build.log File
Created attachment 169502 [details] Environment File
Hiya Wescott, This isn't caused by the patch (both unpack and apply the patches fine on my system). You can spot the proper error messages at the top of your build.log: chmod: cannot access `./patch/030_all_jbj.patch': Function not implemented This looks like it's a problem with chmod -R and isn't directly related to netkit-rsh at all. Can you please include the output from "emerge --info"?
Thanks for the quick reply. This has been a show-stopper for me as I planned already having this server up. > chmod: cannot access `./patch/030_all_jbj.patch': Function not implemented > This looks like it's a problem with chmod -R and isn't directly related to > netkit-rsh at all. I tried to recompile coreutils as it seemed to be the source of the problem, but that emerge fails also. > Can you please include the output from "emerge --info"? Sure, as soon as I get to my lunch break at work I'll go home and post it.
Created attachment 169592 [details] Output of "emerge --info"
Okay, I updated coreutils on another computer that wasn't having this problem and used the resulting quickpkg on the new one, and the problem is still there. That didn't fix it. The reason I thought it might be coreutils is because "equery belongs chmod" returns that package. Apparently thats not the source either. The bug at this point is "rm and chmod return 'Function not implemented' when invoked by emerge".
Thanks, sorry for the delay, I had a rather busy Friday. Could you please check the output of "mount", to check if the /var filesystem is mounted with any special options that might, and that /proc is mounted ([1] suggests that they need to be mounted for chmod and rm to work)... [1] http://osdir.com/ml/linux.pld.devel.english/2006-12/msg00024.html
Oh, yeah that was it. It has been so long since I ran a fresh Gentoo installation. I never had problems for not running mount -o bind /proc /mnt/gentoo/proc before chroot'ing. My web search didn't bring up any relevant results...maybe I need to switch search engines :-/. Anyway, thanks for checking it out. Oh, this also solved another issue that didn't surface until later...a couple packages ignored the X use flag while compiling but reported before merging that it will use that use flag. This was strange, but that is fixed as well.
