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
meta-clang's llvm-config is not compatible with MULTILIBS #247
Comments
Can you cook up a patch ? |
I'm cooking up patches.... 🔨 |
@cosmo0920 is master we have addressed this issue by using |
Yes. Current master's implementation returns empty string on multiarch environment. |
Ok then could you prepare a patch for master as well please ? Usually we do the fix on master before backport to release branches |
thanks for patch, I think this issue is now fixed. |
Yep, this issue is fixed on master. |
Describe the bug
One of the our target boards(RZ/G2E)'s Yocto default conf/local.conf specifies
MULTILIBS = "multilib:lib32"
andDEFAULTTUNE_virtclass-multilib-lib32 = "armv7vethf-neon"
to be able to run 32bit ARMv7 binaries.So, built binaries will be installed in
/usr/lib64/
instead of/usr/lib
.Because our SDK environment does not assume
/usr/lib
for library installation directory.Instead,
/usr/lib64
is used for 64bit libraries and shared object. And/usr/lib32
is used for 32bit objects.ref: https://llvm.org/docs/CMake.html#frequently-used-cmake-variables
To Reproduce
Steps to reproduce the behavior:
MULTILIBS = "multilib:lib32"
andDEFAULTTUNE_virtclass-multilib-lib32 = "armv7vethf-neon"
in local.confError
Expected behavior
meta-clang's llvm-config can work with
DEFAULTTUNE_virtclass-multilib-lib32
specified environment.llvm-config points to ${RECIPE_SYSROOT}/usr/lib/clang/8.0.1/lib/linux/ but actual libclang libraries are put in ${RECIPE_SYSROOT}/usr/lib64/clang/8.0.1/lib/linux/
LLVM insists that using
LLVM_LIBDIR_SUFFIX
to control installation directory suffix such as lib64 or lib32.We should handle library directory glitch it llvm-config with
LLVM_LIBDIR_SUFFIX
.Desktop (please complete the following information):
Additional context
(Updated) I'd encountered this issue during meta-browser's firefox recipe building.
The text was updated successfully, but these errors were encountered: