 |
 |
Just build XRootD from source before you build ROOT. The ROOT team requires you to do that if you want the Python bindings anyway as they're not interested in supporting a bunch of options just for XRootD (which is totally fine).
Well I'm not using any python bindings and root will download xrootd by default (regardless of whether you have python or or not; I have it off) and attempt to build it. I'm in no big hurry for this to work (I have an older root version currently working). I can wait for root to pick up the latest xrootd. They are aware of this problem and was the one who told me to post the errors I was seeing here.
Okay. I'm not part of the XRootD team, but I doubt anyone on it will be against such a PR. Maybe you can start with a minimal failing example (e.g. a build script starting from scratch) that someone can reproduce in a CI workflow and then once that has been clearly demoed contribute a PR that addresses this?
Huh? Failing example? I've already demonstrated that above (with cmake options)! Please read it. I told them which version it was failing. That's why they told me to try to download their master version and see if it builds, which I've confirm that it does. And I really don't have anymore time working on this beyond what I've already put in for this. I have other important priorities to work on.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
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