From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Joseph Kogut <joseph.kogut@gmail.com>,
Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/mesa3d: radeonsi needs wchar
Date: Sun, 25 Oct 2026 21:42:10 +0100 [thread overview]
Message-ID: <at5plTvXu3ikwffX@windsurf> (raw)
In-Reply-To: <20261025131531.45754-1-bernd@kuhls.net>
On Sun, Oct 25, 2026 at 02:15:31PM +0100, Bernd Kuhls wrote:
> BR2_PACKAGE_MESA3D_LLVM depends on BR2_USE_WCHAR, so does
> BR2_PACKAGE_ELFUTILS.
>
> Buildroot commit a24698054b4cf6c994c91d49513bbe5e7b270201 removed the
> dependency to BR2_PACKAGE_MESA3D_LLVM from the radeonsi driver but
> forgot to propagate the dependency to BR2_USE_WCHAR needed by elfutils
> which still is a dependency for the radeonsi driver.
>
> Fixes Kconfig warning:
>
> WARNING: unmet direct dependencies detected for BR2_PACKAGE_ELFUTILS
> Depends on [n]: BR2_USE_WCHAR [=n] && !BR2_STATIC_LIBS [=n] && BR2_TOOLCHAIN_HAS_THREADS [=y]
> Selected by [y]:
> - BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_RADEONSI [=y] && BR2_PACKAGE_MESA3D [=y] && BR2_USE_MMU [=y] && (BR2_i386 [=n] || BR2_x86_64 [=y])
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
I've added a Config.in comment, and applied. Thanks!
Best regards,
Thomas Petazzoni
--
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
prev parent reply other threads:[~2026-10-25 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 13:15 [Buildroot] [PATCH 1/1] package/mesa3d: radeonsi needs wchar Bernd Kuhls
2026-10-25 20:42 ` Thomas Petazzoni via buildroot [this message]
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=at5plTvXu3ikwffX@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=joseph.kogut@gmail.com \
--cc=romain.naour@gmail.com \
--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.