Uh oh!
There was an error while loading. Please reload this page.
GH-43769: [Java] Pin Java JNI CI build to llvm 16 - #43770
Conversation
laurentgo
commented
Aug 20, 2024
I'm a bit confused: is it ORC or Gandiva? |
danepitkin
commented
Aug 20, 2024
From my limited understanding, its ORC that's broken with LLVM 17, but this ORC feature is only used by the Arrow Java Gandiva module. Here's the LLVM issue I was reviewing: llvm/llvm-project#74671 |
In this context, "ORC" is not "Apache ORC". ORC JIT can work with LLVM 17+ but it requires that the main process ( To do this, we have some approaches:
See also: #39695 (comment) If we can't do any of them, we need to pin LLVM 16-. But it's just a workaround because LLVM 16- will reach EOL eventually. |
kou
commented
Aug 20, 2024
I think that we need to create a port for LLVM 16 by ourselves to pin LLVM to 16. Or we can use old vcpkg that uses LLVM 16-. But it will have other problems because other dependencies such as aws-sdk-cpp are also downgraded... |
danepitkin
commented
Aug 20, 2024
Thank you @kou. I'll close this in favor of fixing properly. I'll repost your comment on the issue so the context is not lost. |
Rationale for this change
ORC does not support LLVM 17+ yet.
What changes are included in this PR?
Are these changes tested?
CI
Are there any user-facing changes?
No