From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/mesa3d: DRI drivers need either glx, egl or gbm
Date: Tue, 20 Jul 2021 20:25:45 +0200 [thread overview]
Message-ID: <20210720202545.74d835bd@windsurf> (raw)
In-Reply-To: <20210720172911.15840-1-bernd.kuhls@t-online.de>
Hello Bernd,
On Tue, 20 Jul 2021 19:29:11 +0200
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Fixes build error:
> ../output-1/build/mesa3d-21.1.5/meson.build:520:4:
> ERROR: Problem encountered: building dri drivers require at least one windowing system
>
> OSMesa is not seen as a valid windowing system for DRI drivers anymore:
> https://cgit.freedesktop.org/mesa/mesa/commit/meson.build?h=21.1&id=ee802372180a2b4460cc7abb53438e45c6b6f1e4
>
> Fixes:
> http://autobuild.buildroot.net/results/46e3a66ddc13a064e512aad0f3afd8655889ab9d/
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/mesa3d/Config.in | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
Thanks for the patch. I'm always a bit confused with all these mesa3d
possibilities. How does this patch fit with what you did in commit
15a2f9b819806d38a7d8172a20f80130b1d60e63, where
BR2_PACKAGE_MESA3D_OSMESA_CLASSIC was renamed
BR2_PACKAGE_MESA3D_OSMESA_GALLIUM ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-07-20 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 17:29 [Buildroot] [PATCH 1/1] package/mesa3d: DRI drivers need either glx, egl or gbm Bernd Kuhls
2021-07-20 18:25 ` Thomas Petazzoni [this message]
[not found] ` <20210720202545.74d835bd__29119.6025953226$1626805573$gmane$org@windsurf>
2021-07-20 18:53 ` Bernd Kuhls
2021-08-02 12:40 ` Arnout Vandecappelle
2021-08-07 19:30 ` Peter Korsgaard
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=20210720202545.74d835bd@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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