Description of problem: When Python 3.5 replaced Python 3.4 in Cauldron, various CMake-powered libraries (like hawkey, librepo, libcomps, etc.) failed to detect Python 3.5 properly and thus failed to build. This is fixed in CMake 3.4.0 RC1, which I have provided the necessary RPM SPEC patch Version-Release number of selected component (if applicable): 3.3.2-1.mga6 Reproducible: Steps to Reproduce:
Created attachment 7106 [details] Patch to upgrade CMake to 3.4.0rc1 in Cauldron Added patch referenced in original comment.
Also, see
See Also: (none) => https://bugzilla.redhat.com/show_bug.cgi?id=1269095
Err, sorry. I meant to write, see here the commit that fixes it: https://github.com/Kitware/CMake/commit/2db092b1f60b3677a2d44d5563bec216ae687e2f And the RhBug that identified the problem.
CC: (none) => thierry.vignaud
Please just first upload current cmake version with FC patch: http://pkgs.fedoraproject.org/cgit/cmake.git/tree/cmake-python3.5.patch?id=4798c1522a921a6756ae70b5e64c91d8697b6a88 I've live tested a similar change against /usr/share/cmake/Modules/FindPython* and it enabled me to build libsolv which fails to build with current cmake+py3.5 Else, in case new cmake version failed to build, we'll be be left in frozen hell :-)
Created attachment 7107 [details] Alternate patch to add Python 3.5 detection support to CMake 3.3.2 Added an alternate patch for adding Python 3.5 detection support to CMake 3.3.2
Incidentally, I did test my patch to be sure it built and installed properly on my Cauldron box. I don't know how much that says about it working in iurt, but at least there's that.
I've already pushed cmake 3.4.0-rc1. I'm closing this as FIXED.
Status: NEW => RESOLVEDCC: (none) => jani.valimaaResolution: (none) => FIXED