From: Adam Ford <aford173@gmail.com>
To: buildroot@buildroot.org
Cc: Raphael Pavlidis <raphael.pavlidis@gmail.com>,
Adam Ford <aford173@gmail.com>
Subject: [Buildroot] [PATCH] package/x11r7/xwayland: add mesa3d ordering dependency
Date: Thu, 16 Jul 2026 08:30:41 -0500 [thread overview]
Message-ID: <20260716133041.2147516-1-aford173@gmail.com> (raw)
Xwayland's glamor/DRI configure check looks for Mesa's dri.pc in staging.
Without an explicit ordering dependency, a highly parallel build can run
Xwayland's configure before mesa3d is installed, failing with:
ERROR: Dependency "dri" not found
Add mesa3d to XWAYLAND_DEPENDENCIES when it is enabled.
Signed-off-by: Adam Ford <aford173@gmail.com>
diff --git a/package/x11r7/xwayland/xwayland.mk b/package/x11r7/xwayland/xwayland.mk
index 2b8513602c..bce9a572ab 100644
--- a/package/x11r7/xwayland/xwayland.mk
+++ b/package/x11r7/xwayland/xwayland.mk
@@ -30,6 +30,14 @@ XWAYLAND_CONF_OPTS = \
-Ddtrace=false \
-Ddocs=false
+# Xwayland's glamor/DRI configure check needs Mesa's dri.pc in staging.
+# Without an explicit ordering dependency, a highly parallel build can run
+# Xwayland's configure before mesa3d is installed, failing with:
+# ERROR: Dependency "dri" not found
+ifeq ($(BR2_PACKAGE_MESA3D),y)
+XWAYLAND_DEPENDENCIES += mesa3d
+endif
+
ifeq ($(BR2_PACKAGE_HAS_LIBEGL)$(BR2_PACKAGE_LIBEPOXY),yy)
XWAYLAND_CONF_OPTS += -Dglamor=true
XWAYLAND_DEPENDENCIES += libepoxy
--
2.53.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-07-16 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 13:30 Adam Ford [this message]
2026-07-16 19:30 ` [Buildroot] [PATCH] package/x11r7/xwayland: add mesa3d ordering dependency John Ernberg
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=20260716133041.2147516-1-aford173@gmail.com \
--to=aford173@gmail.com \
--cc=buildroot@buildroot.org \
--cc=raphael.pavlidis@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;
as well as URLs for NNTP newsgroup(s).