-
-
Notifications
You must be signed in to change notification settings - Fork 12.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cling: Fix build on Ventura #131473
cling: Fix build on Ventura #131473
Conversation
Fixes: CMake Error at CMakeLists.txt:647 (message): Unable to find Python interpreter, required for builds and testing.
|
I've asked upstream for a new release: root-project/cling#492 (comment) |
@iMichka are you sure it's a cling issue? Sounds like you are missing |
Cling uses LLVM 9 in current release, which includes a Google Benchmark with issue. Looks like LLVM 12+ has newer version with fix (llvm/llvm-project@b498303), which would be available if Cling does a new release as they are now on LLVM 13 - root-project/cling@19442ce Workaround would be to patch their code with fix (google/benchmark@3d1c267) or to use a temporary |
Oh I see -- the problem is with LLVM 9. Well, what I've done in my version of cling is linked it dynamically against LLVM and Clang. Not sure if that helps you or not. |
Not sure to understand what you mean. Is there something actionnable on our side? |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
|
Does not build on Ventura I asked for a new release in May 2023, the response was not super clear: root-project/cling#492 (comment) The comments on #131473 did also not really look helpful. Download count is low, so deprecating is the best thing to do, and gives upstream some more time to react before removal on our side.
Fixes:
CMake Error at CMakeLists.txt:647 (message):
Unable to find Python interpreter, required for builds and testing.
brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingbrew install --build-from-source <formula>
)? If this is a new formula, does it passbrew audit --new <formula>
?