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 V2] package/x11r7/xwayland: fix glamor DRI ordering dependency on mesa3d
Date: Mon, 3 Aug 2026 09:08:15 -0500 [thread overview]
Message-ID: <20260803140815.617446-1-aford173@gmail.com> (raw)
Xwayland's glamor support enables a DRI configure check that 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
Since mesa3d is what provides the DRI/EGL/GBM bits glamor relies on, fold
it into the glamor condition: only enable -Dglamor=true and add it to the
dependencies alongside libepoxy.
Signed-off-by: Adam Ford <aford173@gmail.com>
diff --git a/package/x11r7/xwayland/xwayland.mk b/package/x11r7/xwayland/xwayland.mk
index 02a21b96c1..3bd87a4552 100644
--- a/package/x11r7/xwayland/xwayland.mk
+++ b/package/x11r7/xwayland/xwayland.mk
@@ -32,7 +32,7 @@ XWAYLAND_CONF_OPTS = \
ifeq ($(BR2_PACKAGE_HAS_LIBEGL)$(BR2_PACKAGE_LIBEPOXY),yy)
XWAYLAND_CONF_OPTS += -Dglamor=true
-XWAYLAND_DEPENDENCIES += libepoxy
+XWAYLAND_DEPENDENCIES += libepoxy mesa3d
else
XWAYLAND_CONF_OPTS += -Dglamor=false
endif
--
2.53.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-08-03 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 14:08 Adam Ford [this message]
2026-08-09 17:44 ` [Buildroot] [PATCH V2] package/x11r7/xwayland: fix glamor DRI ordering dependency on mesa3d John Ernberg
2026-08-11 19:12 ` Adam Ford
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=20260803140815.617446-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 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.