Ok, I think we are on the same page now. The underlying problem is that CMake cannot find the Python headers due to the unconventional install layout of pyenv. Maybe there's something we can improve on the XRootD side to make the installation work out of the box, but I'd rather do this as part of the rewrite of the Python packaging, which is starting to show its age. For now, if you set CMAKE_PREFIX_PATH as I suggested, it works. There are two ways of setting it, one way is from the command line with -DCMAKE_PREFIX_PATH=... which you obviously cannot do, and the other is by just setting it as an environment variable. In your container, if you run the pip install command as shown below, it will work:

$ env CMAKE_PREFIX_PATH=/home/docker/.pyenv/versions/3.10.4 python3.10 -m pip --verbose install 'xrootd==5.5.2'

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1474#issuecomment-1429237071", "url": "https://github.com/xrootd/xrootd/issues/1474#issuecomment-1429237071", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

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