Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>,
	openembedded-core@lists.openembedded.org,
	"Khem Raj" <raj.khem@gmail.com>,
	"Zoltán Böszörményi" <zboszor@gmail.com>
Subject: Re: [OE-core] [PATCH v4 0/9] mesa: upgrade to 25.0.2
Date: Wed, 2 Apr 2025 04:45:30 +0300	[thread overview]
Message-ID: <0926082a-b09e-4d8d-8199-671823db87bd@oss.qualcomm.com> (raw)
In-Reply-To: <CANNYZj_aEritSc0Te9hWR+OZVQ1DDFY0b4A0Q0H148L5YjEKcw@mail.gmail.com>

On 01/04/2025 19:28, Alexander Kanavin wrote:
> On Tue, 1 Apr 2025 at 18:19, Dmitry Baryshkov via
> lists.openembedded.org
> <dmitry.baryshkov=oss.qualcomm.com@lists.openembedded.org> wrote:
>>> ERROR: mesa-native-2_25.0.2-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-53842/tmp/work/x86_64-linux/mesa-native/25.0.2/temp/run.do_compile.506477' failed with exit code 1
>>> ...
>>> | FAILED: src/intel/shaders/intel_gfx80_shaders.spv
>>> | /srv/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-53842/tmp/work/x86_64-linux/mesa-native/25.0.2/build/src/compiler/clc/mesa_clc ../mesa-25.0.2/src/intel/shaders/libintel_shaders.h ../mesa-25.0.2/src/intel/shaders/generate.cl ../mesa-25.0.2/src/intel/shaders/generate_draws.cl ../mesa-25.0.2/src/intel/shaders/generate_draws_iris.cl ../mesa-25.0.2/src/intel/shaders/query_copy.cl ../mesa-25.0.2/src/intel/shaders/util.cl -o src/intel/shaders/intel_gfx80_shaders.spv -- -DNDEBUG=1 -DGFX_VERx10=80 -I/srv/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-53842/tmp/work/x86_64-linux/mesa-native/25.0.2/mesa-25.0.2/src/intel/shaders/. -I/srv/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-53842/tmp/work/x86_64-linux/mesa-native/25.0.2/mesa-25.0.2/src/compiler/libcl -I/srv/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-53842/tmp/work/x86_64-linux/mesa-native/25.0.2/mesa-25.0.2/src -I/srv/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-53842/tmp/work/x86_64-linux/mesa-native/25.0.2/mesa-25.0.2/src/intel -I/srv/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-53842/tmp/work/x86_64-linux/mesa-native/25.0.2/build/src/intel -I/srv/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-53842/tmp/work/x86_64-linux/mesa-native/25.0.2/mesa-25.0.2/src/intel/genxml
>>> | /bin/sh: 1: /srv/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-53842/tmp/work/x86_64-linux/mesa-native/25.0.2/build/src/compiler/clc/mesa_clc: not found
>>
>>
>> I've fixed all other issues, except the x32 (working on reproducing it
>> now) and this one. Would you have a pointer to the build job?
> 
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/1264/steps/14/logs/stdio
> 
> This is in context of oe-selftest, but it is simply building
> qemu-system-native on debian 12 - I suspect the mesa-native fail is
> specific to that host distro. I can try to reproduce if you need help
> with it.

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).

-- 
With best wishes
Dmitry

  reply	other threads:[~2025-04-02  1:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-31 12:21 [PATCH v4 0/9] mesa: upgrade to 25.0.2 Dmitry Baryshkov
2025-03-31 12:21 ` [PATCH v4 1/9] llvm: move libLLVM.so.N.M to llvm-libllvm package Dmitry Baryshkov
2025-03-31 12:21 ` [PATCH v4 2/9] llvm: use OECMAKE_SOURCEPATH to specify cmake dir Dmitry Baryshkov
2025-03-31 12:21 ` [PATCH v4 3/9] llvm: handle libdir in llvm-config Dmitry Baryshkov
2025-03-31 12:21 ` [PATCH v4 4/9] llvm: also use llvm-config wrapper for nativesdk recipes Dmitry Baryshkov
2025-03-31 12:21 ` [PATCH v4 5/9] llvm: support building libclc Dmitry Baryshkov
2025-03-31 12:21 ` [PATCH v4 6/9] llvm: add SPIRV-LLVM-Translator support Dmitry Baryshkov
2025-03-31 12:21 ` [PATCH v4 7/9] mesa: upgrade 24.0.7 -> 25.0.2 Dmitry Baryshkov
2025-03-31 12:21 ` [PATCH v4 8/9] bindgen-cli: a tool to generate Rust bindings Dmitry Baryshkov
2025-03-31 12:21 ` [PATCH v4 9/9] mesa: add support for RustiCL under PACKAGECONFIG "opencl" Dmitry Baryshkov
2025-04-01  7:40 ` [OE-core] [PATCH v4 0/9] mesa: upgrade to 25.0.2 Mathieu Dubois-Briand
2025-04-01  8:06   ` Alexander Kanavin
2025-04-01  8:27   ` Mathieu Dubois-Briand
2025-04-01  8:41     ` Alexander Kanavin
2025-04-01 16:19   ` Dmitry Baryshkov
2025-04-01 16:28     ` Alexander Kanavin
2025-04-02  1:45       ` Dmitry Baryshkov [this message]
2025-04-02  6:55         ` Mathieu Dubois-Briand
2025-04-02  7:56           ` Alexander Kanavin
2025-04-02 12:50             ` Dmitry Baryshkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0926082a-b09e-4d8d-8199-671823db87bd@oss.qualcomm.com \
    --to=dmitry.baryshkov@oss.qualcomm.com \
    --cc=alex.kanavin@gmail.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=zboszor@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox