Created attachment 409226 [details] build.log Setting CMAKE_MAKEFILE_GENERATOR="emake" make pykde4 install fine. NOTE: I forced cmake generator to ninja via make.conf, as it usually speeds up compilation, especially for larger packages.
What is the suggested solution - force emake generator in the package?
As emake still is the default I don't think forcing it in the ebuild is not necessary. But I think it is good to catch such failures early. This topic (+solution) came up in the forums, so there are users who set ninja globally. IMHO it is better to track this in bugzilla and not the forums. And probably one day cmake-herd decides to fully go ninja ;) then a tracker bug is good to have.
(In reply to Michael Palimaka (kensington) from comment #1) > What is the suggested solution - force emake generator in the package? We need to overwrite the user choice here for sane build. (In reply to Franz Fellner from comment #2) > As emake still is the default I don't think forcing it in the ebuild is not > necessary. But I think it is good to catch such failures early. This topic > (+solution) came up in the forums, so there are users who set ninja > globally. IMHO it is better to track this in bugzilla and not the forums. It's better to fix it instead of having it just for the record. > And probably one day cmake-herd decides to fully go ninja ;) then a tracker > bug is good to have. There is no cmake-herd -> kde is maintaining cmake-utils.eclass.
Thanks for reporting. This is fixed in git now, by forcing the default makefile generator. Please sync to get the changes. https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3a955da58910bb2fbd7c9341724d5f23b3de6eed
