Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@smile.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/mesa3d: fix drisw build without dri3
Date: Wed, 7 Feb 2024 16:19:20 +0100	[thread overview]
Message-ID: <20240207161920.61fb7da9@windsurf> (raw)
In-Reply-To: <20240206124947.1617078-2-romain.naour@smile.fr>

On Tue,  6 Feb 2024 13:49:46 +0100
Romain Naour <romain.naour@smile.fr> wrote:

> mesa3d 23.3 added dri3_priv.h header and dri3_check_multibuffer() function in
> drisw (part of swrast gallium driver) that can be build without dri3.
> 
>   i686-buildroot-linux-gnu/bin/ld: src/glx/libglx.a.p/drisw_glx.c.o: in function `driswCreateScreenDriver':
>   drisw_glx.c:(.text.driswCreateScreenDriver+0x3a0): undefined reference to `dri3_check_multibuffer'
>   collect2: error: ld returned 1 exit status
> 
> Add HAVE_DRI3 guard around dri3_priv.h header and the zink code using
> dri3_check_multibuffer().
> 
> While testing again the TestGlxinfo runtime test, a new unexpected error line
> appeared in the glxinfo log:
> 
>   MESA-LOADER: failed to open zink: /usr/lib/dri/zink_dri.so
> 
> mesa3d try to load zink gallium driver even if it was not enabled at
> build time, indeed there is no such option in Buildroot.
> 
> Apply patches sent upstream:
> https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27478
> 
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/6093854455
> 
> Signed-off-by: Romain Naour <romain.naour@smile.fr>
> ---
>  .../0006-drisw-fix-build-without-dri3.patch   | 58 +++++++++++++++++++
>  ...on-t-try-zink-if-not-enabled-in-mesa.patch | 42 ++++++++++++++
>  2 files changed, 100 insertions(+)
>  create mode 100644 package/mesa3d/0006-drisw-fix-build-without-dri3.patch
>  create mode 100644 package/mesa3d/0007-glxext-don-t-try-zink-if-not-enabled-in-mesa.patch

Both applied. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-02-07 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 12:49 [Buildroot] [PATCH 0/2] TestGlxinfo fixes Romain Naour
2024-02-06 12:49 ` [Buildroot] [PATCH 1/2] package/mesa3d: fix drisw build without dri3 Romain Naour
2024-02-07 15:19   ` Thomas Petazzoni via buildroot [this message]
2024-02-06 12:49 ` [Buildroot] [PATCH 2/2] support/testing: use core2duo cpu emulation for TestGlxinfo Romain Naour

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=20240207161920.61fb7da9@windsurf \
    --to=buildroot@buildroot.org \
    --cc=romain.naour@smile.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox