Please read tips for efficient and successful posting and posting code
Please fill also the fields below. Note that root -b -q will tell you this info, and starting from 6.28/06 upwards, you can call .forum bug from the ROOT prompt to pre-populate a topic.
_ROOT Version:6.28/06
_Platform:Rocky Linux 8.10
_Compiler:GCC 8.5.0
When I first installed 6.28.06 from source on Rocky Linux system ( ~ 8.5 ? ) which had Python 2.7 and 3.6 from the system no extra aguments were needed for CMake to find the include and library files ( as confirmed by the CMakeCache.txt file ) , pyroot was set to ON by default and a libPyROOT.so library was created ( for python3.6 )
RL8.10 currently offers another two versions of python 3.11 and 3.12 and I’d like to compile 6.28.06 against either of them . If I simply run cmake without any options I end up with pyroot being turned off ( according to the last lines of the config output ) . If I force it on ( -Dpyroot=ON ) then the config output indicated it is on and CMakeCache.txt is populated with the expected values for PYTHON_EXECUTABLE, PYTHON_INCLUDE_DIRS and PYTHON_LIBRARIES etc. but no libPyROOT.so is ever made and I did not notice any error messages anywhere .
Specifying PYTHON_EXECUTABLE on the cmake line as well as -Dpyroot=ON also results in no libPyROOT.so being generated no matter which version I set it to.
Is it a question of cmake not being able to handle multiple python3 versions ? Any hints at where I should look for why it fails ? From the CMakeCache.txt file it appears that no matter what version I use in the cmake the pointers get set correctly.
One other thing - libPyMVA.so builds fine.
Upgrading to a newer version of ROOT is not really an ( easy ) option for this particular application.
peter