Seems like the error is that I'm missing the "/usr/portage/dev-util/cmake/files/cmake-2.8.4-FindPythonLibs.patch" but I can't seem to figure out where I'm supposed to get the patch from. Any help would be appreciated.

Last edited by SaltyPeanut on Mon Sep 10, 2012 3:09 am; edited 1 time in total

Made my own ebuild with the patch file, seemed to fix the issue. I guess I could have also put the patch file in the /etc/portage/dev-util/cmake/files/ directory, but I didn't want to mess with the main tree.

I note that the missing patch file seems to have been deleted from the main tree sometime earlier this evening, so maybe this was just some oversight error. Anyway, cmake compiled now when I replaced the patch file, and hopefully I didn't break anything too bad.

That is exactly the workaround which I was going to suggest after checking that the file was absent and still called for in the current version of that ebuild, the former would indicate a problem with your copy of the tree whereas the latter would just mean another emerge --sync would be in order, within the usual guidelines for such. As it is, this is a known bug and the developers maintaining that package have been notified.

That is exactly the workaround which I was going to suggest after checking that the file was absent and still called for in the current version of that ebuild, the former would indicate a problem with your copy of the tree whereas the latter would just mean another emerge --sync would be in order, within the usual guidelines for such. As it is, this is a known bug and the developers maintaining that package have been notified.

And with that, welcome to the forums.

Thanks. I am a bit confused as to why the patch was removed; the change log seems to indicate that portage 2.2+ users won't need it? But last I checked, the portage package is still at 2.1 (at least that is what packages.gentoo.org shows me). I guess we'll be seeing some new changes pushed through in the next few days?

So far as I can tell, from the relatively quick check that I made, it appears to have been removed on the assumption that it was no longer necessary for versions remaining in the tree. Once the bug is resolved, which I suspect will be within a day, we should know with more certainty.