mesa: Upgrade to 26.2.0
PATCH v3 1/3 mesa: Upgrade to 26.2.0
Release notes:
https://lists.freedesktop.org/archives/mesa-dev/2026-August/226690.html
Removed upstream 0001-gallivm-Fix-armhf-build-against-LLVM-22.patch Adapted 0001-freedreno-don-t-encode-build-path-into-binaries.patch
--- ...on-t-encode-build-path-into-binaries.patch | 17 +++++++----- ...livm-Fix-armhf-build-against-LLVM-22.patch | 27 ------------------- meta/recipes-graphics/mesa/mesa.inc | 5 ++-- 3 files changed, 13 insertions(+), 36 deletions(-) delete mode 100644 meta/recipes-graphics/mesa/files/0001-gallivm-Fix-armhf-build-against-LLVM-22.patch
meta/recipes-graphics/mesa/files/0001-freedreno-don-t-encode-build-path-into-binaries.patch +11 -6
@@ -1,4 +1,4 @@ -From 266f7047df67d500223b66f7eb9d8779be4f4ad1 Mon Sep 17 00:00:00 2001 +From 1ae1feb55885c8ec26ed2ef148fa75c6240d9804 Mon Sep 17 00:00:00 2001 From: Dmitry Baryshkov <[email protected]> Date: Wed, 10 Dec 2025 02:27:16 +0200 Subject: [PATCH] freedreno: don't encode build path into binaries
@@ -25,7 +25,7 @@ Signed-off-by: Quentin Schulz <[email protected]> 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/src/freedreno/meson.build b/src/freedreno/meson.build -index e8f01b8..8144a75 100644 +index e8f01b880bc..8144a75bd1c 100644 --- a/src/freedreno/meson.build +++ b/src/freedreno/meson.build @@ -4,9 +4,10 @@
@@ -42,13 +42,18 @@ index e8f01b8..8144a75 100644 dep_libarchive = dependency('libarchive', allow_fallback: true, required: false, disabler : true) dep_libxml2 = dependency('libxml-2.0', allow_fallback: true, required: false) diff --git a/src/freedreno/registers/meson.build b/src/freedreno/registers/meson.build -index f4be681..cd0caaf 100644 +index 9318ce48fe5..8d2b305d202 100644 --- a/src/freedreno/registers/meson.build +++ b/src/freedreno/registers/meson.build -@@ -43,4 +43,6 @@ if install_fd_decode_tools - endforeach - endif +@@ -16,6 +16,8 @@ freedreno_copyright = files(copyright_file) + + freedreno_xml_header_files = [] +devenv.set('RNN_PATH', meson.current_source_dir()) + subdir('adreno') + + foreach f : xml_adreno_files +-- +2.55.0 +
meta/recipes-graphics/mesa/files/0001-gallivm-Fix-armhf-build-against-LLVM-22.patch deleted +0 -27
@@ -1,27 +0,0 @@ -From 8db6e909c3a540d31a73b79a0792e927cc2c6e83 Mon Sep 17 00:00:00 2001 -From: Alessandro Astone <[email protected]> -Date: Sun, 1 Mar 2026 18:14:09 +0100 -Subject: [PATCH] gallivm: Fix armhf build against LLVM 22 - -StringMapIterator<bool> became StringMapIterBase<bool, false /* IsConst */>; -Use `auto` to handle either case. - -Upstream-Status: Submitted [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/40161] -Signed-off-by: Jose Quaresma <[email protected]> ---- - src/gallium/auxiliary/gallivm/lp_bld_misc.cpp | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/src/gallium/auxiliary/gallivm/lp_bld_misc.cpp b/src/gallium/auxiliary/gallivm/lp_bld_misc.cpp -index ce8ca02..86779f0 100644 ---- a/src/gallium/auxiliary/gallivm/lp_bld_misc.cpp -+++ b/src/gallium/auxiliary/gallivm/lp_bld_misc.cpp -@@ -331,7 +331,7 @@ lp_build_fill_mattrs(std::vector<std::string> &MAttrs) - llvm::sys::getHostCPUFeatures(features); - #endif - -- for (llvm::StringMapIterator<bool> f = features.begin(); -+ for (auto f = features.begin(); - f != features.end(); - ++f) { - MAttrs.push_back(((*f).second ? "+" : "-") + (*f).first().str());
meta/recipes-graphics/mesa/mesa.inc +2 -3
@@ -17,14 +17,13 @@ PE = "2" SRC_URI = "https://archive.mesa3d.org/mesa-${PV}.tar.xz \ file://0001-meson-misdetects-64bit-atomics-on-mips-clang.patch \ file://0001-freedreno-don-t-encode-build-path-into-binaries.patch \ - file://0001-gallivm-Fix-armhf-build-against-LLVM-22.patch \ file://0001-src-intel-compiler-jay-jay_ir.h-do-not-used-typed-en.patch \ file://0001-src-intel-compiler-jay-fix-GCC-10-case-label-declara.patch \ file://0001-src-util-u_math.c-do-not-use-arm-fpu-instructions-if.patch \ " -SRC_URI[sha256sum] = "5296b88a0f1e012e2cb9ada150a2bbadf728ca81e5a4fb2ab43c83a4d2158606" -PV = "26.1.6" +SRC_URI[sha256sum] = "efd4bb08cdb7c365a812cd4e6c9202ab55b2f22cdcd13c7d6c4f9647b799a4ef" +PV = "26.2.0" UPSTREAM_CHECK_GITTAGREGEX = "mesa-(?P<pver>\d+(\.\d+)+)"
Signature · 1 line
2.55.0
PATCH v3 2/3 mesa-libclc: New recipe for forking libclc for Rusticl purposes in Mesa
See the reasoning and discussion at
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/43020
which was merged and backported to 26.2.0.
TL;DR: LLVM constantly introduces breaking changes that cause regressions for running OpenCL CTS with Rusticl and finally Karol Herbst had enough.
This fork is from the LLVM 22 version of libclc and contains the necessary fixes to make Rusticl pass OpenCL CTS.
--- meta/conf/distro/include/maintainers.inc | 1 + .../mesa/mesa-libclc_22.1.8.3.bb | 26 +++++++++++++++++++ 2 files changed, 27 insertions(+) create mode 100644 meta/recipes-graphics/mesa/mesa-libclc_22.1.8.3.bb
meta/conf/distro/include/maintainers.inc +1 -0
@@ -524,6 +524,7 @@ RECIPE_MAINTAINER:pn-menu-cache = "Ross Burton <[email protected]>" RECIPE_MAINTAINER:pn-mesa = "Unassigned <[email protected]>" RECIPE_MAINTAINER:pn-mesa-demos = "Unassigned <[email protected]>" RECIPE_MAINTAINER:pn-mesa-gl = "Unassigned <[email protected]>" +RECIPE_MAINTAINER:pn-mesa-libclc = "Zoltán Böszörményi <[email protected]>" RECIPE_MAINTAINER:pn-mesa-tools-native = "Unassigned <[email protected]>" RECIPE_MAINTAINER:pn-meson = "Trevor Gamblin <[email protected]>" RECIPE_MAINTAINER:pn-meta-environment-${MACHINE} = "Richard Purdie <[email protected]>"
meta/recipes-graphics/mesa/mesa-libclc_22.1.8.3.bb new file +26 -0
@@ -0,0 +1,26 @@ +SUMMARY = "Mesa fork of libclc: Implementation of the library requirements of the OpenCL C programming language." +HOMEPAGE = "https://gitlab.freedesktop.org/karolherbst/mesa-libclc/" +SECTION = "devel" +LICENSE = "Apache-2.0-with-LLVM-exception" +LIC_FILES_CHKSUM = "file://LICENSE.TXT;md5=7cc795f6cbb2d801d84336b83c8017db" + +SRC_URI = "git://gitlab.freedesktop.org/karolherbst/mesa-libclc.git;protocol=https;branch=llvm_22" + +SRCREV = "87f66007242ff10e9e84bf32be84f9057f6abc75" + +inherit cmake pkgconfig + +# Depend explicitly on clang-native instead of using TOOLCHAIN as the build +# objects from this recipe are build explicitly using clang for GPU targets. +# We could INHIBIT_DEFAULT_DEPS to avoid any other toolchain but then we need +# to wrestle CMake to configure without a toolchain. +DEPENDS += "clang-native spirv-llvm-translator-native" + +# Semicolon-separated list of targets to build +LIBCLC_TARGETS ?= "all" + +EXTRA_OECMAKE += "-DLIBCLC_TARGETS_TO_BUILD='${LIBCLC_TARGETS}'" + +FILES:${PN} += "${datadir}/mesa-clc" + +BBCLASSEXTEND = "native nativesdk"
Signature · 1 line
2.55.0
PATCH v3 3/3 mesa, mesa-tools-native: Use mesa-libclc
In reply to Zoltán BöszörményiAccording to the release notes at
https://lists.freedesktop.org/archives/mesa-dev/2026-August/226690.html
| One important note for packagers is that there is now a Mesa community | maintained libclc fork that is verified to pass the OpenCL CTS with | Mesa/Rusticl, and will fix bugs after an upstream libclc major release | branch goes EoL. The Mesa build system will pick it up when available, | and fall back to upstream libclc if not. This libclc fork is not | verified for any other usages or users of libclc outside of Mesa.
Rusticl would complain if about not this libclc fork is used due to OpenCL CTS compliance.
--- meta/recipes-graphics/mesa/mesa-tools-native.bb | 2 +- meta/recipes-graphics/mesa/mesa.inc | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-graphics/mesa/mesa-tools-native.bb +1 -1
@@ -11,7 +11,7 @@ PACKAGECONFIG += "gallium-llvm" # to PACKAGECONFIG like in mesa.inc PACKAGECONFIG += "${@bb.utils.filter('DISTRO_FEATURES', 'x11 wayland', d)}" -DEPENDS += "libclc-native spirv-tools-native spirv-llvm-translator-native" +DEPENDS += "mesa-libclc-native spirv-tools-native spirv-llvm-translator-native" EXTRA_OEMESON += " \ -Dmesa-clc=enabled -Dinstall-mesa-clc=true -Dmesa-clc-bundle-headers=enabled \
meta/recipes-graphics/mesa/mesa.inc +2 -2
@@ -109,7 +109,7 @@ PACKAGECONFIG[opengl] = "-Dopengl=true, -Dopengl=false" # "opencl" also requires libclc and gallium-llvm to be present in PACKAGECONFIG! # Be sure to enable them both for the target and for the native build. -PACKAGECONFIG[opencl] = "-Dgallium-rusticl=true -Dmesa-clc-bundle-headers=enabled, -Dgallium-rusticl=false, bindgen-cli-native clang libclc spirv-tools spirv-llvm-translator" +PACKAGECONFIG[opencl] = "-Dgallium-rusticl=true -Dmesa-clc-bundle-headers=enabled, -Dgallium-rusticl=false, bindgen-cli-native clang mesa-libclc spirv-tools spirv-llvm-translator" X11_DEPS = "xorgproto virtual/libx11 libxext libxxf86vm libxdamage libxfixes xrandr xorgproto libxshmfence" # "x11" requires "opengl"
@@ -253,7 +253,7 @@ RPROVIDES:libopencl-mesa += "virtual-opencl-icd" RPROVIDES:libgles2-mesa += "libgles3-mesa" RPROVIDES:libgles2-mesa-dev += "libgles3-mesa-dev" -RDEPENDS:libopencl-mesa += "${@bb.utils.contains('PACKAGECONFIG', 'opencl', 'libclc', '', d)}" +RDEPENDS:libopencl-mesa += "${@bb.utils.contains('PACKAGECONFIG', 'opencl', 'mesa-libclc', '', d)}" PACKAGES =+ "libegl-mesa libegl-mesa-dev \ libgallium \
Signature · 1 line
2.55.0
Re: [OE-core] [PATCH v3 3/3] mesa, mesa-tools-native: Use mesa-libclc
Quoted 61 lines · Zoltan Boszormenyi via lists.openembedded.org
According to the release notes at
https://lists.freedesktop.org/archives/mesa-dev/2026-August/226690.html| One important note for packagers is that there is now a Mesa community | maintained libclc fork that is verified to pass the OpenCL CTS with | Mesa/Rusticl, and will fix bugs after an upstream libclc major release | branch goes EoL. The Mesa build system will pick it up when available, | and fall back to upstream libclc if not. This libclc fork is not | verified for any other usages or users of libclc outside of Mesa.Rusticl would complain if about not this libclc fork is used due to OpenCL CTS compliance.
Signed-off-by Zoltán Böszörményi <[email protected]>--- meta/recipes-graphics/mesa/mesa-tools-native.bb | 2 +- meta/recipes-graphics/mesa/mesa.inc | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)meta/recipes-graphics/mesa/mesa-tools-native.bb +0
-0@@ -11,7 +11,7 @@ PACKAGECONFIG += "gallium-llvm" # to PACKAGECONFIG like in mesa.inc PACKAGECONFIG += "${@bb.utils.filter('DISTRO_FEATURES', 'x11 wayland',d)}"
meta/recipes-graphics/mesa/mesa-tools-native.bb +1
-1-DEPENDS += "libclc-native spirv-tools-native spirv-llvm-translator-native" +DEPENDS += "mesa-libclc-native spirv-tools-nativespirv-llvm-translator-native"
EXTRA_OEMESON+= " \
-Dmesa-clc=enabled -Dinstall-mesa-clc=truemeta/recipes-graphics/mesa/mesa-tools-native.bb +0
-1-Dmesa-clc-bundle-headers=enabled \meta/recipes-graphics/mesa/mesa.inc +0
-0@@ -109,7 +109,7 @@ PACKAGECONFIG[opengl] = "-Dopengl=true, -Dopengl=false" # "opencl" also requires libclc and gallium-llvm to be present inPACKAGECONFIG!
# Be sure to enable them both for the target and for the native build.meta/recipes-graphics/mesa/mesa.inc +0
-2-PACKAGECONFIG[opencl] = "-Dgallium-rusticl=true -Dmesa-clc-bundle-headers=enabled, -Dgallium-rusticl=false,bindgen-cli-native clang libclc spirv-tools spirv-llvm-translator"
meta/recipes-graphics/mesa/mesa.inc +1
-1+PACKAGECONFIG[opencl] = "-Dgallium-rusticl=true -Dmesa-clc-bundle-headers=enabled, -Dgallium-rusticl=false,bindgen-cli-native clang mesa-libclc spirv-tools spirv-llvm-translator"
X11_DEPS= "xorgproto virtual/libx11 libxext libxxf86vm libxdamage
libxfixes xrandr xorgproto libxshmfence"
# "x11" requires "opengl"meta/recipes-graphics/mesa/mesa.inc +0
-1@@ -253,7 +253,7 @@ RPROVIDES:libopencl-mesa += "virtual-opencl-icd" RPROVIDES:libgles2-mesa += "libgles3-mesa" RPROVIDES:libgles2-mesa-dev += "libgles3-mesa-dev" -RDEPENDS:libopencl-mesa += "${@bb.utils.contains('PACKAGECONFIG',
Quoted 4 lines
'opencl', 'libclc', '', d)}"
+RDEPENDS:libopencl-mesa += "${@bb.utils.contains('PACKAGECONFIG', 'opencl', 'mesa-libclc', '', d)}"
Is it possible to have both versions installed side-by-side on the target? I'm asking this because there might be a collision between the fork and the original.
Jose
Quoted 18 lines
PACKAGES =+ "libegl-mesa libegl-mesa-dev \ libgallium \--
2.55.0-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#242898):
https://lists.openembedded.org/g/openembedded-core/message/242898
Mute This Topic: https://lists.openembedded.org/mt/120622539/10043485
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH v3 3/3] mesa, mesa-tools-native: Use mesa-libclc
Quoted 54 lines · Jose Quaresma
Quoted 50 lines · Zoltan Boszormenyi via lists.openembedded.org
According to the release notes at
https://lists.freedesktop.org/archives/mesa-dev/2026-August/226690.html| One important note for packagers is that there is now a Mesa community | maintained libclc fork that is verified to pass the OpenCL CTS with | Mesa/Rusticl, and will fix bugs after an upstream libclc major release | branch goes EoL. The Mesa build system will pick it up when available, | and fall back to upstream libclc if not. This libclc fork is not | verified for any other usages or users of libclc outside of Mesa.Rusticl would complain if about not this libclc fork is used due to OpenCL CTS compliance.
Signed-off-by Zoltán Böszörményi <[email protected]>--- meta/recipes-graphics/mesa/mesa-tools-native.bb | 2 +- meta/recipes-graphics/mesa/mesa.inc | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)meta/recipes-graphics/mesa/mesa-tools-native.bb +1
-1@@ -11,7 +11,7 @@ PACKAGECONFIG += "gallium-llvm" # to PACKAGECONFIG like in mesa.inc PACKAGECONFIG += "${@bb.utils.filter('DISTRO_FEATURES', 'x11 wayland', d)}" -DEPENDS += "libclc-native spirv-tools-native spirv-llvm-translator-native" +DEPENDS += "mesa-libclc-native spirv-tools-native spirv-llvm-translator-native" EXTRA_OEMESON += " \ -Dmesa-clc=enabled -Dinstall-mesa-clc=true -Dmesa-clc-bundle-headers=enabled \meta/recipes-graphics/mesa/mesa.inc +1
-1@@ -109,7 +109,7 @@ PACKAGECONFIG[opengl] = "-Dopengl=true, -Dopengl=false" # "opencl" also requires libclc and gallium-llvm to be present in PACKAGECONFIG! # Be sure to enable them both for the target and for the native build. -PACKAGECONFIG[opencl] = "-Dgallium-rusticl=true -Dmesa-clc-bundle-headers=enabled, -Dgallium-rusticl=false, bindgen-cli-native clang libclc spirv-tools spirv-llvm-translator" +PACKAGECONFIG[opencl] = "-Dgallium-rusticl=true -Dmesa-clc-bundle-headers=enabled, -Dgallium-rusticl=false, bindgen-cli-native clang mesa-libclc spirv-tools spirv-llvm-translator" X11_DEPS = "xorgproto virtual/libx11 libxext libxxf86vm libxdamage libxfixes xrandr xorgproto libxshmfence" # "x11" requires "opengl"@@ -253,7 +253,7 @@ RPROVIDES:libopencl-mesa += "virtual-opencl-icd" RPROVIDES:libgles2-mesa += "libgles3-mesa" RPROVIDES:libgles2-mesa-dev += "libgles3-mesa-dev"
Quoted 5 lines
meta/recipes-graphics/mesa/mesa.inc RPROVIDES:libopencl-mesa += "virtual-opencl-icd" · line 256
Quoted 2 lines
meta/recipes-graphics/mesa/mesa.inc +1
-1-RDEPENDS:libopencl-mesa += "${@bb.utils.contains('PACKAGECONFIG', 'opencl', 'libclc', '', d)}" +RDEPENDS:libopencl-mesa += "${@bb.utils.contains('PACKAGECONFIG', 'opencl', 'mesa-libclc', '', d)}"Is it possible to have both versions installed side-by-side on the target?
Yes. libclc and mesa-libclc can be installed side-by-side. Only meta-libclc will be used by mesa, if built with that, though.
Quoted 1 line
I'm asking this because there might be a collision between the fork and the original.
There is none.
The installation directory and the pkg-config file are renamed in the fork.
Quoted 19 lines
Jose
Quoted 16 lines
meta/recipes-graphics/mesa/mesa.inc +0
-1PACKAGES =+ "libegl-mesa libegl-mesa-dev \ libgallium \ --2.55.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#242898): https://lists.openembedded.org/g/openembedded-core/message/242898
Mute This Topic: https://lists.openembedded.org/mt/120622539/10043485
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH v3 3/3] mesa, mesa-tools-native: Use mesa-libclc
Quoted 79 lines · Zoltan Boszormenyi
Quoted 4 lines · Jose Quaresma
On Thu, Aug 6, 2026 at 6:15 AM Zoltan Boszormenyi via
Quoted 14 lines · lists.openembedded.org
Quoted 14 lines
According to the release notes at
https://lists.freedesktop.org/archives/mesa-dev/2026-August/226690.html| One important note for packagers is that there is now a Mesa community | maintained libclc fork that is verified to pass the OpenCL CTS with | Mesa/Rusticl, and will fix bugs after an upstream libclc major release | branch goes EoL. The Mesa build system will pick it up when available, | and fall back to upstream libclc if not. This libclc fork is not | verified for any other usages or users of libclc outside of Mesa.Rusticl would complain if about not this libclc fork is used due to OpenCL CTS compliance.
Quoted 7 lines
Review
Quoted 7 lines
Signed-off-by Zoltán Böszörményi <[email protected]>--- meta/recipes-graphics/mesa/mesa-tools-native.bb | 2 +- meta/recipes-graphics/mesa/mesa.inc | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)(quoted diff) +0
-0b/meta/recipes-graphics/mesa/mesa-tools-native.bb
Quoted 6 lines
meta/recipes-graphics/mesa/mesa-tools-native.bb PACKAGECONFIG += "gallium-llvm" · line 12
Quoted 6 lines
index
20207450bf..c495d2e8a8100644meta/recipes-graphics/mesa/mesa-tools-native.bb +0
-0@@ -11,7 +11,7 @@ PACKAGECONFIG += "gallium-llvm" # to PACKAGECONFIG like in mesa.inc PACKAGECONFIG += "${@bb.utils.filter('DISTRO_FEATURES', 'x11 wayland',d)}"
Quoted 2 lines
meta/recipes-graphics/mesa/mesa-tools-native.bb PACKAGECONFIG += "gallium-llvm" · line 13
Quoted 2 lines
meta/recipes-graphics/mesa/mesa-tools-native.bb +0
-1-DEPENDS += "libclc-native spirv-tools-nativespirv-llvm-translator-native"
Quoted 1 line
meta/recipes-graphics/mesa/mesa-tools-native.bb PACKAGECONFIG += "gallium-llvm" · line 13
Quoted 1 line
meta/recipes-graphics/mesa/mesa-tools-native.bb +1
-0+DEPENDS += "mesa-libclc-native spirv-tools-nativespirv-llvm-translator-native"
Quoted 3 lines
meta/recipes-graphics/mesa/mesa-tools-native.bb PACKAGECONFIG += "gallium-llvm" · line 15
Quoted 3 lines
meta/recipes-graphics/mesa/mesa-tools-native.bb +0
-0EXTRA_OEMESON += " \ -Dmesa-clc=enabled -Dinstall-mesa-clc=true-Dmesa-clc-bundle-headers=enabled \
Quoted 1 line
Review
Quoted 1 line
(quoted diff) +0
-0b/meta/recipes-graphics/mesa/mesa.inc
Quoted 4 lines
meta/recipes-graphics/mesa/mesa.inc PACKAGECONFIG[opengl] = "-Dopengl=true,
Quoted 4 lines
index
a50b900cf2..fa51d62bfc100644meta/recipes-graphics/mesa/mesa.inc +0
-0@@ -109,7 +109,7 @@ PACKAGECONFIG[opengl] = "-Dopengl=true,-Dopengl=false"
Quoted 2 lines
meta/recipes-graphics/mesa/mesa.inc PACKAGECONFIG[opengl] = "-Dopengl=true, · line 109
Quoted 2 lines
meta/recipes-graphics/mesa/mesa.inc +0
-0# "opencl" also requires libclc and gallium-llvm to be present inPACKAGECONFIG!
Quoted 2 lines
meta/recipes-graphics/mesa/mesa.inc PACKAGECONFIG[opengl] = "-Dopengl=true, · line 111
Quoted 2 lines
meta/recipes-graphics/mesa/mesa.inc +0
-1# Be sure to enable them both for the target and for the native build. -PACKAGECONFIG[opencl] = "-Dgallium-rusticl=true-Dmesa-clc-bundle-headers=enabled, -Dgallium-rusticl=false, bindgen-cli-native clang libclc spirv-tools spirv-llvm-translator"
Quoted 1 line
meta/recipes-graphics/mesa/mesa.inc PACKAGECONFIG[opengl] = "-Dopengl=true, · line 111
Quoted 1 line
meta/recipes-graphics/mesa/mesa.inc +1
-0+PACKAGECONFIG[opencl] = "-Dgallium-rusticl=true-Dmesa-clc-bundle-headers=enabled, -Dgallium-rusticl=false, bindgen-cli-native clang mesa-libclc spirv-tools spirv-llvm-translator"
Quoted 2 lines
meta/recipes-graphics/mesa/mesa.inc PACKAGECONFIG[opengl] = "-Dopengl=true, · line 112
Quoted 2 lines
meta/recipes-graphics/mesa/mesa.inc +0
-0X11_DEPS = "xorgproto virtual/libx11 libxext libxxf86vm libxdamagelibxfixes xrandr xorgproto libxshmfence"
Quoted 6 lines
meta/recipes-graphics/mesa/mesa.inc RPROVIDES:libopencl-mesa += "virtual-opencl-icd" · line 256
Quoted 6 lines
meta/recipes-graphics/mesa/mesa.inc +0
-1# "x11" requires "opengl"@@ -253,7 +253,7 @@ RPROVIDES:libopencl-mesa += "virtual-opencl-icd" RPROVIDES:libgles2-mesa += "libgles3-mesa" RPROVIDES:libgles2-mesa-dev += "libgles3-mesa-dev" -RDEPENDS:libopencl-mesa += "${@bb.utils.contains('PACKAGECONFIG','opencl', 'libclc', '', d)}"
Quoted 1 line
meta/recipes-graphics/mesa/mesa.inc RPROVIDES:libopencl-mesa += "virtual-opencl-icd" · line 256
Quoted 1 line
meta/recipes-graphics/mesa/mesa.inc +1
-0+RDEPENDS:libopencl-mesa += "${@bb.utils.contains('PACKAGECONFIG','opencl', 'mesa-libclc', '', d)}"
Quoted 3 lines
Is it possible to have both versions installed side-by-side on the
target?
Quoted 9 lines
Yes. libclc and mesa-libclc can be installed side-by-side. Only meta-libclc will be used by mesa, if built with that, though.
Quoted 1 line
I'm asking this because there might be a collision between the fork and
the original.
There is none.
The installation directory and the pkg-config file are renamed in the fork.
Nice! Thanks
Quoted 23 lines
Quoted 15 lines
Jose
Quoted 11 lines
meta/recipes-graphics/mesa/mesa.inc +0
-1PACKAGES =+ "libegl-mesa libegl-mesa-dev \ libgallium \ --2.55.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#242898):https://lists.openembedded.org/g/openembedded-core/message/242898
Quoted 3 lines
Quoted 3 lines
Mute This Topic: https://lists.openembedded.org/mt/120622539/10043485
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [Quoted 2 lines
Quoted 2 lines
-=-=-=-=-=-=-=-=-=-=-=-
Quoted 8 lines · Zoltan Boszormenyi via lists.openembedded.org
Release notes:
https://lists.freedesktop.org/archives/mesa-dev/2026-August/226690.htmlRemoved upstream 0001-gallivm-Fix-armhf-build-against-LLVM-22.patch Adapted 0001-freedreno-don-t-encode-build-path-into-binaries.patch
Signed-off-by Zoltán Böszörményi <[email protected]>---
Hi Zoltán,
I believe you need to remove or refresh another patch:
ERROR: mesa-2_26.2.0-r0 do_patch: Applying patch '/srv/pokybuild/yocto-worker/genericx86-64/build/layers/openembedded-core/meta/recipes-graphics/mesa/files/0001-src-intel-compiler-jay-jay_ir.h-do-not-used-typed-en.patch' on target directory '/srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work/core2-64-poky-linux/mesa/26.2.0/sources/mesa-26.2.0' CmdError('quilt --quiltrc /srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work/core2-64-poky-linux/mesa/26.2.0/recipe-sysroot-native/etc/quiltrc push', 1, 'stdout: Applying patch 0001-src-intel-compiler-jay-jay_ir.h-do-not-used-typed-en.patch
patching file src/intel/compiler/jay/jay_ir.h
https://autobuilder.yoctoproject.org/valkyrie/#/builders/4/builds/4342
This happens in virtually all configurations. Can you have a look at the issue?
Thanks,
Mathieu
Signature · 3 lines
Mathieu Dubois-Briand, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
2026. 08. 07. 7:02 keltezéssel, Mathieu Dubois-Briand írta:
Quoted 13 lines · Zoltan Boszormenyi via lists.openembedded.org
Quoted 8 lines
Release notes:
https://lists.freedesktop.org/archives/mesa-dev/2026-August/226690.htmlRemoved upstream 0001-gallivm-Fix-armhf-build-against-LLVM-22.patch Adapted 0001-freedreno-don-t-encode-build-path-into-binaries.patch
Signed-off-by Zoltán Böszörményi <[email protected]>---
Hi Zoltán,
I believe you need to remove or refresh another patch:
Quoted 8 lines
ERROR: mesa-2_26.2.0-r0
do_patch: Applying patch '/srv/pokybuild/yocto-worker/genericx86-64/build/layers/openembedded-core/meta/recipes-graphics/mesa/files/0001-src-intel-compiler-jay-jay_ir.h-do-not-used-typed-en.patch' on target directory '/srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work/core2-64-poky-linux/mesa/26.2.0/sources/mesa-26.2.0' CmdError('quilt --quiltrc/srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work/core2-64-poky-linux/mesa/26.2.0/recipe-sysroot-native/etc/quiltrcpush', 1, 'stdout: Applying patch 0001-src-intel-compiler-jay-jay_ir.h-do-not-used-typed-en.patch
patching filesrc/intel/compiler/jay/jay_ir.hhttps://autobuilder.yoctoproject.org/valkyrie/#/builders/4/builds/4342
This happens in virtually all configurations. Can you have a look at the issue?
Sorry about that.
I only tested the change with wrynose before sending it.
The v4 series fixes this problem.
FWIW, there was another patch that was removed due to its contents being already upstream. The commit message in v4 reflects that.
Quoted 4 lines
Thanks,
Mathieu