grpc: Update llvm-19 Konan dependency path after Kotlin compiler upgrade #522
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Mr3zee
approved these changes
Oct 27, 2025
Collaborator
Author
|
Yes, I will add it. It's basically running it, getting the error including the path, comparing it to the currently used one, replacing the path from the error with the current one xD |
Mr3zee
pushed a commit
that referenced
this pull request
Nov 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Subsystem
gRPC/Native
Problem Description
After the recent upgrade to Koltin 2.2.21 compilation for Linux failed because a LLVM 19 Konan dependency path changed.
Solution
The Bazel toolchain now uses the correct, updated dependency path to include header files.
Unfortunately we will have to update this path everytime we upgrade the Kotlin compiler version. I couldn't find a way to automatically determine the dependency paths.