Closed hejamu closed 5 months ago
I don't know if it's any help, but I notice libint v2.6 is using the old find_package(PythonInterp)
detection. It's whatever cmake detects for the Python cmd that gets substituted in at https://github.com/evaleev/libint/blob/v2.6.0/export/cmake/CMakeLists.txt.export#L308 line that you're hitting. Newer v2.8 libint uses find_package(Python)
. (This shows up as ${PYTHON_EXECUTABLE}
(old) vs. ${Python_EXECUTABLE}
(new) at https://github.com/evaleev/libint/blob/master/export/cmake/CMakeLists.txt.export#L512 ). I hope the newer detection can find python3
if python
doesn't exist, as your situation seems widespread.
I agree with @loriab mentioned, python detection has been updated to the latest CMake module. Please upgrade to 2.8.1, this problem should not occur.
Building libint fails if
python
is not a defined command (as is standard on Ubuntu). I stumbled across this in the cp2k toolchain.Changing the command to
python3
would fix this inconvenience of needing to define thepython
command.