Hey,<br /><br />Desired outcome is for mesa meson configure to succeeded by updating<br />RUNPATH on llvm-config native binary required by mesa when gallium-llvm<br />included. When running bitbake -c devshell mesa. Then chrpath -l on llvm-config<br /><br />Should return on TARGET_ARCH x86_64<br />$ORIGIN/../lib64:$ORIGIN/../../lib64<br />not <br />$ORIGIN/../lib:$ORIGIN/../../lib<br /><br />SNAPSHOT OF FAILURE<br />*************************************************************************************************************************<br />File "/../../../mesa/&lt;version&gt;/recipe-sysroot-native/usr/lib/python3.11/re/__init__.py", line 223, in finditer<br />return _compile(pattern, flags).finditer(string)<br />^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br />TypeError: expected string or bytes-like object, got 'NoneType'<br />*************************************************************************************************************************<br /><br />Reason for above failure, at least for me, when TARGET_ARCH = x86_64 you run into<br />bellow when running llvm-config --help or variant commands directly.<br /><br />llvm-config: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory<br /><br />Because of that when mesa configure executes llvm-config --version the string is not returned. Thus, leading<br />to above error.<br /><br />If you run chrpath -l on llvm-config you see<br /><br />$ORIGIN/../lib:$ORIGIN/../../lib:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::<br /><br />When target architecture is x86_64 those folders don't exists in recipe-sysroot of a recipe that requires llvm-native.<br /><br />The llvm_sysroot_preprocess_native function in current MR addresses that problem by<br />making RUNPATH target architecture dependent.<br /><br />As to why RUNPATH includes both the original RUNPATH and the update target architecture<br />dependent directory name the llvm recipe requires the llvm-native llvm-config binary to<br />compile, but the build libs are stored in lib directory not lib64. Tried everything I could<br />think of change that not much can be done about that. When llvm-native gets included<br />in another recipe however libs are located at $ORIGIN/../lib64:$ORIGIN/../../lib64, at least<br />for TARGET ARCH x86_64.<br /><br />As for the second problem llvm-config --libdir returns<br /><br />/../../../../../../mesa/2_22.2.2-r0/recipe-sysroot/usr/lib<br /><br />instead of<br /><br />/../../../../../../mesa/2_22.2.2-r0/recipe-sysroot/usr/lib64<br /><br />Which causes mesa configure to fail as ../../mesa/2_22.2.2-r0/recipe-sysroot/usr/lib doesn't exist.<br /><br />According to <a href="https://github.com/llvm/llvm-project/blob/a11cd0d94ed3cabf0998a0289aead05da94c86eb/llvm/CMakeLists.txt#L399" target="_blank" rel="noopener">https://github.com/llvm/llvm-project/blob/a11cd0d94ed3cabf0998a0289aead05da94c86eb/llvm/CMakeLists.txt#L399</a><br />and <a href="https://github.com/llvm/llvm-project/blob/a11cd0d94ed3cabf0998a0289aead05da94c86eb/llvm/CMakeLists.txt#L389" target="_blank" rel="noopener">https://github.com/llvm/llvm-project/blob/a11cd0d94ed3cabf0998a0289aead05da94c86eb/llvm/CMakeLists.txt#L389</a><br /><span class="pl-smi"><br />LLVM_LIBDIR_SUFFIX variable is used to set </span>command. MR addresses that by setting the <span class="pl-smi">LLVM_LIBDIR_SUFFIX<br />variable. The reason I decided to use HOST_ARCH instead of TARGET_ARCH is because bitbake sets<br />HOST_ARCH = "${TARGET_ARCH}" in bitbake.conf, but I'll admit there's ignorance on my part in terms<br />of what I think that variable is set to and what class-native it used for.<br /><br />:)<br /></span>
<div id=":pf" class="a3s aiL "><wbr /></div>