From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@buildroot.org
Cc: Daniel Lang <dalang@gmx.at>,
El Mehdi YOUNES <elmehdi.younes@smile.fr>,
Joseph Kogut <joseph.kogut@gmail.com>,
Romain Naour <romain.naour@gmail.com>,
Valentin Korenblit <valentinkorenblit@gmail.com>
Subject: [Buildroot] [PATCH v2 5/6] package/mesa3d: i915 Gallium driver needs llvm
Date: Sun, 20 Sep 2026 23:39:05 +0200 [thread overview]
Message-ID: <20260920213906.905956-5-bernd@kuhls.net> (raw)
In-Reply-To: <20260920213906.905956-1-bernd@kuhls.net>
Buildroot commit 3e296a151195f9d32dbfd62d6c75d08b822be6dd bumped the
package to 25.3.0 which includes upstream commit
https://gitlab.freedesktop.org/mesa/mesa/-/commit/b8b38d38b1c14b60de0324ac2f98ff7f1f4cc3c5
that enforces llvm for the i915 gallium driver causing configure errors
in buildroot:
../output-1/build/mesa3d-26.1.6/meson.build:241:3: ERROR: Feature llvm
cannot be disabled: i915 Gallium driver requires LLVM for vertex shaders
Please note that
https://gitlab.freedesktop.org/mesa/mesa/-/commit/4235c39a9a8378f1e2dc0899dd4c3c941f27b887
later removed the llvm dependency for the r300 driver introduced by the
commit mentioned above so we only need to add the dependency to the i915
driver.
The configure option draw-use-llvm is disabled by default when llvm is
not available:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/37c7d19e46a4863c120186a99ac0344c2dd31260
Fixes:
https://autobuild.buildroot.org/results/acd9039901cf4168e6318c62252ddae6ea0ec93d/
Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
---
v2: no changes
package/mesa3d/Config.in | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/package/mesa3d/Config.in b/package/mesa3d/Config.in
index e18d25eb8e..f45a675445 100644
--- a/package/mesa3d/Config.in
+++ b/package/mesa3d/Config.in
@@ -147,11 +147,15 @@ config BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_FREEDRENO
config BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_I915
bool "Gallium i915 driver"
depends on BR2_i386 || BR2_x86_64
+ depends on BR2_PACKAGE_MESA3D_LLVM
select BR2_PACKAGE_MESA3D_GALLIUM_DRIVER
select BR2_PACKAGE_LIBDRM_INTEL
help
Support for i915-based Intel GPUs.
+comment "i915 driver needs llvm"
+ depends on !BR2_PACKAGE_MESA3D_LLVM
+
config BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_IRIS
bool "Gallium iris driver"
depends on BR2_PACKAGE_LLVM_ARCH_SUPPORTS # host-llvm
--
2.47.3
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-09-20 21:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 21:39 [Buildroot] [PATCH v2 1/6] package/llvm-project/libclc: apply mesa-libclc patch set Bernd Kuhls
2026-09-20 21:39 ` [Buildroot] [PATCH v2 2/6] package/mesa3d: rework OpenCL handling Bernd Kuhls
2026-09-20 21:39 ` [Buildroot] [PATCH v2 3/6] package/mesa3d: precomp-compiler does not need target llvm Bernd Kuhls
2026-09-20 21:39 ` [Buildroot] [PATCH v2 4/6] package/mesa3d: crocus Gallium driver needs precomp-compiler Bernd Kuhls
2026-09-20 21:39 ` Bernd Kuhls [this message]
2026-09-20 21:39 ` [Buildroot] [PATCH v2 6/6] package/{mesa3d, mesa3d-headers}: bump version to 26.2.3 Bernd Kuhls
2026-10-03 21:19 ` Julien Olivain via buildroot
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=20260920213906.905956-5-bernd@kuhls.net \
--to=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=dalang@gmx.at \
--cc=elmehdi.younes@smile.fr \
--cc=joseph.kogut@gmail.com \
--cc=romain.naour@gmail.com \
--cc=valentinkorenblit@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.