But as of now if someone were to build root from source (having openssl3 as their default openssl version), the version of xrootd that root downloads won't build for openssl3. All details of that has already be shown above.
...
In any case, the solution at least for me is to wait for a newer version of root that will download the latest version of xrootd so it will compile against openssl3.

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). There's no need to wait. As you're already building ROOT from source this will be very straightforward for you.

... I'd recommend to use find_package or for newer cmake versions FindOpenSSL (it basically uses find_package underneath it) to set openssl include/libs location because it will likely order those includes correctly.

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?

xrootd should be setup to build with a versions of openssl, that's not necessarily the default version (e.g. not in the nominal system directories), after all that's why cmake provided the various openssl options.

It can. c.f. PR #1661 for exactly such an example.

In any case, the solution at least for me is to wait for a newer version of root that will download the latest version of xrootd so it will compile against openssl3.

PS, I didn't use brew (to install root). I was building root from source since I needed it to be built with C++17 on.

Yes, that was clear. I hope it was clear from the PR that I was talking about using brew to only install dependencies.

—
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/1649#issuecomment-1074625022", "url": "https://github.com/xrootd/xrootd/issues/1649#issuecomment-1074625022", "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