 |
 |
I understand more now. So after poking around the sdist from `python -m pip download 'xrootd==5.5.2'` I think I understand the problem better. Something we all agree on is that if https://github.com/xrootd/xrootd/blob/76c1f87c3d9cc5ff3432a0daf93361956c7abb08/cmake/XRootDFindLibs.cmake#L182 fails then you'll get an error message like ``` -- Could NOT find PythonLibs (missing: PYTHON_LIBRARIES PYTHON_INCLUDE_DIRS) (Required is at least version "3.11") ``` which is uncontroversial. Though if that happens then `BUILD_PYTHON` is `FALSE` https://github.com/xrootd/xrootd/blob/76c1f87c3d9cc5ff3432a0daf93361956c7abb08/cmake/XRootDFindLibs.cmake#L187-L192 and then the directory [`$startdir/xrootdbuild/bindings/python`](https://github.com/xrootd/xrootd/blob/76c1f87c3d9cc5ff3432a0daf93361956c7abb08/packaging/wheel/install.sh#L4) never gets created https://github.com/xrootd/xrootd/blob/76c1f87c3d9cc5ff3432a0daf93361956c7abb08/bindings/CMakeLists.txt#L2-L4 and https://github.com/xrootd/xrootd/blob/76c1f87c3d9cc5ff3432a0daf93361956c7abb08/packaging/wheel/install.sh#L40 fails ungracefully as there is no directory to navigate to. So there are two problems: 1. CMake is not finding valid Python libraries and include directories for `pyenv` virtual environments. 2. https://github.com/xrootd/xrootd/blob/76c1f87c3d9cc5ff3432a0daf93361956c7abb08/packaging/wheel/install.sh#L40 isn't guarded from configurations where it doesn't exist. -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1474#issuecomment-1429169978 You are receiving this because you are subscribed to this thread. Message ID: <[log in to unmask]> ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1