 |
 |
@simonmichal , thanks for following up! I see this issue in the logs now, so it makes sense that it's not being found. However, I'm fairly certain that I have the set of python dev libraries and headers since I routinely compile against python for generating bindings with pybind11, for example (I haven't found a helpful list of files that python3.7-dev installs - for example, this seems pretty minimal: https://packages.ubuntu.com/bionic/amd64/python3.7-dev/filelist. But I assume it's the headers + libraries) Based on the above, I suspect the issue may be that my python is installed via pyenv (I'm on a cluster, so I can't install python centrally) My headers are at `$PYENV_ROOT/versions/3.9.2/include/python3.9`, and the libraries are at `$PYENV_ROOT/versions/3.9.2/lib`. Would it be possible for me to manually pass those paths directly to xrootd since it's not finding them automatically? (Can I pass cmake options through pip? Usually I would just modify the CMakeLists, but that may not be such an easy option here) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1474#issuecomment-903944717 ######################################################################## 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