llvm_19.1.6: port latest LLVM version and fix the cross-compilation config LLVM_HOST_TRIPLE #199
+304
−0
Conversation
This file contains 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
hashraf91
changed the title
We are experiencing issue with EGL initialization. As mesa depends on LLVM for llvmpipe driver, so porting the latest version available as of today which seems to fix the issue. Ported from: openembedded/openembedded-core@8546473 JIRA-ID: SB-24074 Tested-by: Ahsan Hussain <[email protected]> Signed-off-by: Haseeb Ashraf <[email protected]>
hashraf91
force-pushed
the
SB-24074
branch
2 times, most recently
from
0e78604 to
ac7889b
Compare
| # --------------------------------------------------------------------------------------------------------------------- | ||
|
|
||
| EXTRA_OECMAKE:append:class-target = " -DLLVM_HOST_TRIPLE=${TARGET_SYS}" | ||
| EXTRA_OECMAKE:append:class-nativesdk = " -DLLVM_HOST_TRIPLE=${TARGET_SYS}" |
There was a problem hiding this comment.
Why change for class-nativesdk? Isn't it for SDKMACHINE
There was a problem hiding this comment.
class-nativesdk is for SDK which could also built for different arch. See the original recipe: https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-devtools/llvm/llvm_19.1.6.bb#L89
There was a problem hiding this comment.
Okay, this should be SDK_SYS. Thanks for pointing this out.
The correct way to configure cmake for cross-compilation includes setting the LLVM_HOST_TRIPLE as well. Documentation Ref: https://github.com/llvm/llvm-project/blob/llvmorg-19.1.6/llvm/docs/HowToCrossCompileLLVM.rst#configuring-cmake This fixes the bug when LLVM is cross-compiled for AAarch64 but it was getting built with the triple of native build system instead of the TARGET_SYS ('aarch64-oe-linux' in my case). ``` No available targets are compatible with triple "x86_64-unknown-linux-gnu" ``` JIRA-ID: SB-24074 Signed-off-by: Haseeb Ashraf <[email protected]>
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.
We are experiencing issue with EGL initialization. As mesa depends on LLVM for llvmpipe driver, so porting the latest version available as of today which seems to fix the issue.
Ported from:
openembedded/openembedded-core@8546473
Tested-by: Ahsan Hussain [email protected]
Signed-off-by: Haseeb Ashraf [email protected]
The correct way to configure cmake for cross-compilation includes setting the LLVM_HOST_TRIPLE as well. This fixes the bug when LLVM is cross-compiled for AAarch64 but it was getting built with the triple of native build system instead of the TARGET_SYS ('aarch64-oe-linux' in my case).
Documentation Ref:
https://github.com/llvm/llvm-project/blob/llvmorg-19.1.6/llvm/docs/HowToCrossCompileLLVM.rst#configuring-cmake
JIRA-ID: SB-24074
Signed-off-by: Haseeb Ashraf [email protected]