Re: [OE-core] [PATCH v4 0/9] mesa: upgrade to 25.0.2

[Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>]

On 02/04/2025 10:56, Alexander Kanavin wrote:
> On Wed, 2 Apr 2025 at 08:55, Mathieu Dubois-Briand
> <mathieu.dubois-briand@bootlin.com> wrote:
>   >
>>> It's really strange as my build host is Debian 12. And it's even more
>>> strange as mesa-clc was built few lines above (16406).
>>
>> Ok, I will try to play a bit with it today, let's see if I can reproduce
>> easily.
> 
> I took v4, and ran 'bitbake mesa-native' on the exact build host
> (debian-12-vk-1) where it happened, and it built without issues.
> mesa_clc is built and used in build logs.
> 
> If this happens again, we should take care to preserve the failing
> build directory, so it can be inspected post-mortem. 'Not found' error
> can be misleading: it may mean there's a problem with one of the
> libraries, or the executable is somehow in an incorrect format, etc.

Okay, I was able to reproduce the issue. It happens when the llvm-native 
was built with a different build-dir as the current build, because then 
the other build-dir (which might not exist ATM) crawls into llvm-config 
--ldflags.

For example, I caught this while doing builds in build-test, while the 
sstate-cache contained llvm-native build from the build-test-st (from 
selftests builds).

-- 
With best wishes
Dmitry