> > The Python_EXECUTABLE is workaround that can be applied to a spec file.
>
> OK, that is clear. If PYTHON_EXECUTABLE no longer works that is a well
> understandable issue.
>
> Something like this maybe?
>
> --- a/CMakeLists.txt
> +++ b/CMakeLists.txt
> @@ -216,6 +216,9 @@ endif()
>
> # Use Python modules based on CMake version for backward compatibility
> set(CYTHON_EXECUTABLE "")
> +if (${PYTHON_EXCUTABLE})
> + set(Python_EXECUTABLE ${PYTHON_EXCUTABLE})
> +endif()
> if (${CMAKE_VERSION} VERSION_LESS "3.12")
> # Look for Python. We prefer some variant of python 3 if the system has it
> FIND_PACKAGE(PythonInterp 3 QUIET)
>
> Jason
Jason,
After a lot of more testing, I have found that the tip of the master branch is ok!
These patches resolve the issue:
5dcc1f402 Improve python searching logic in buildscripts.
462a8737 build: Fix cmake warning
Technically, the earlier patch is the one that breaks the -D, and the second fixes that.
On a system with two python 3 interpreters, when PYTHON_EXECUTABLE is NOT passed in from the command line,
the pyverbs is not built as expected, but the build otherwise works.
When it is, the pyverbs is built.
We can pull these two patches back to fix the issue to earlier versions as we need.
Thanks for your help!
Mike
