From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Alsey Coleman Miller <alseycmiller@gmail.com>
Cc: buildroot@buildroot.org, "André Zwing" <nerv@dawncrow.de>
Subject: Re: [Buildroot] [PATCH v2 1/2] package/libxkbcommon: build libxkbregistry when libxml2 is available
Date: Sun, 9 Aug 2026 22:28:32 +0200 [thread overview]
Message-ID: <anjixKjxRvjrCYok@windsurf> (raw)
In-Reply-To: <20260809201403.3855903-1-alseycmiller@gmail.com>
On Sun, Aug 09, 2026 at 04:14:02PM -0400, Alsey Coleman Miller wrote:
> libxkbregistry is the keyboard layout catalogue half of the library. It
> parses the XML layout registry and so needs libxml2, which is presumably
> why it was disabled unconditionally rather than wired to a dependency.
>
> wine needs it. Its configure.ac requires XKBREGISTRY_LIBS alongside
> wayland-client, wayland-scanner, xkbcommon and linux/input.h before it
> will build the Wayland driver, and wine.mk passes --with-wayland for any
> build with BR2_PACKAGE_WAYLAND - which turns that notice into a hard
> error:
>
> checking for wayland-client.h... yes
> checking for wl_display_connect in -lwayland-client... yes
> checking for wayland-scanner... .../host/bin/wayland-scanner
> checking for xkb_context_new in -lxkbcommon... yes
> checking for wayland-egl.h... yes
> checking for wl_egl_window_create in -lwayland-egl... yes
> configure: error: Wayland development files not found, the Wayland
> driver won't be supported.
> This is an error since --with-wayland was requested.
>
> Every other term of that test passes; only XKBREGISTRY_LIBS is empty, so
> wine and wayland together could not be built on any architecture.
>
> Gated on BR2_PACKAGE_LIBXML2 rather than turned on outright, because
> meson.build takes dependency('libxml-2.0') unconditionally once
> enable-xkbregistry is set, so a target without libxml2 would fail to
> configure.
>
> Regarding since when this is broken, three pieces had to come together:
>
> - libxkbcommon has passed -Denable-xkbregistry=false since commit
> 1791bc30a5 ("package/libxkbcommon: bump version to 1.0.1", Sep 2020),
> i.e. Buildroot 2020.11. libxkbregistry has therefore never been built
> in Buildroot.
>
> - wine's configure gained the XKBREGISTRY_LIBS term in its Wayland
> test in wine 9.0, with upstream commit d64ea8e4a6c9
> ("winewayland.drv: Enumerate Xkb layouts and create matching HKL.",
> Nov 2023).
>
> - wine.mk started passing --with-wayland in commit 7cb49e7712
> ("package/wine: bump to version 9.19", Oct 2024), which is what turns
> the missing XKBREGISTRY_LIBS from a notice into a hard error.
>
> The breakage therefore dates from Buildroot 2024.11, and every branch
> since is affected, including the LTS one: 2025.02.x carries wine 10.0,
> whose configure has the XKBREGISTRY_LIBS check, together with
> libxkbcommon 1.9.2 built with -Denable-xkbregistry=false, and its wine.mk
> passes --with-wayland. 2025.05.x and 2025.08.x are in the same state.
> A backport to 2025.02.x is thus needed.
>
> Signed-off-by: Alsey Coleman Miller <alseycmiller@gmail.com>
Thanks for this new iteration!
Reviewed-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-08-09 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 20:14 [Buildroot] [PATCH v2 1/2] package/libxkbcommon: build libxkbregistry when libxml2 is available Alsey Coleman Miller
2026-08-09 20:14 ` [Buildroot] [PATCH v2 2/2] package/wine: select libxkbcommon and libxml2 for the Wayland driver Alsey Coleman Miller
2026-08-09 20:29 ` Thomas Petazzoni via buildroot
2026-08-09 20:28 ` Thomas Petazzoni via buildroot [this message]
2026-08-10 9:51 ` [Buildroot] [PATCH v2 1/2] package/libxkbcommon: build libxkbregistry when libxml2 is available Raphaël Gallais-Pou
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=anjixKjxRvjrCYok@windsurf \
--to=buildroot@buildroot.org \
--cc=alseycmiller@gmail.com \
--cc=nerv@dawncrow.de \
--cc=thomas.petazzoni@bootlin.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.