public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: raj.khem@gmail.com, openembedded-core@lists.openembedded.org
Cc: Changqing Li <changqing.li@windriver.com>
Subject: Re: [OE-core] [PATCH] mesa-tools-native: fix do_compile failure
Date: Wed, 25 Mar 2026 15:45:13 +0100	[thread overview]
Message-ID: <f4ed8844-38e7-49bb-9363-822af85f5012@cherry.de> (raw)
In-Reply-To: <20260325073954.1176537-1-khem.raj@oss.qualcomm.com>

Hi Khem, Changqing,

On 3/25/26 8:39 AM, Khem Raj via lists.openembedded.org wrote:
> From: Changqing Li <changqing.li@windriver.com>
> 
> Fix do_compile failure:
> ../sources/mesa-26.0.1/src/panfrost/lib/kmod/pan_kmod.c:7:10: fatal error: xf86drm.h: No such file or directory
> 

What's the setup for this failure?

> Signed-off-by: Changqing Li <changqing.li@windriver.com>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
>   meta/recipes-graphics/mesa/mesa-tools-native.bb | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-graphics/mesa/mesa-tools-native.bb b/meta/recipes-graphics/mesa/mesa-tools-native.bb
> index 50d2f5cbb0..743e3391e9 100644
> --- a/meta/recipes-graphics/mesa/mesa-tools-native.bb
> +++ b/meta/recipes-graphics/mesa/mesa-tools-native.bb
> @@ -11,7 +11,7 @@ PACKAGECONFIG += "gallium-llvm"
>   # to PACKAGECONFIG like in mesa.inc
>   PACKAGECONFIG += "${@bb.utils.filter('DISTRO_FEATURES', 'x11 wayland', d)}"
>   
> -DEPENDS += "libclc-native spirv-tools-native spirv-llvm-translator-native"
> +DEPENDS += "libclc-native spirv-tools-native spirv-llvm-translator-native libdrm-native"
>   

libdrm-native is brought in via the wayland PACKAGECONFIG, which is 
enabled if DISTRO_FEATURES has it, so I'm assuming this issue can be 
reproduced on non-wayland setups?

Reading the code...

src/panfrost/lib/kmod/meson.build

clearly highlights there's a dependency on libdrm (dep_libdrm), but 
dep_libdrm (created in meson.build) isn't created as a required 
dependency, while it probably should since 
src/panfrost/lib/kmod/panfrost_kmod.c clearly calls functions from 
xf86drm.h which are only defined in the lib. Maybe something to patch in 
mesa itself as well, so that it complains it cannot build the tool 
because of missing libdrm dependency.

libdrm is apparently necessary for DRI, GBM and any Vulkan driver (see 
with_dri2 in meson.build). DRI is true when building Gallium drivers (we 
have this correct in PACKAGECONFIG[gallium]).
We would need to check but I'm assuming we're missing the libdrm 
dependency in PACKAGECONFIG[vulkan] if we're building without gallium in 
PACKAGECONFIG.
That still wouldn't fix the missing libdrm dependency for panfrost tool 
though, for that I'm suggesting we add it to mesa.inc via:

TOOLS_DEPS:append = "${@bb.utils.contains('PACKAGECONFIG', 'panfrost', 
'libdrm ', '', d)}"

to match what we're doing for the freedreno tool.

Cheers,
Quentin


  parent reply	other threads:[~2026-03-25 14:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25  7:39 [PATCH] mesa-tools-native: fix do_compile failure Khem Raj
2026-03-25 12:51 ` [OE-core] " Alexander Kanavin
2026-03-25 14:46   ` Khem Raj
2026-03-25 14:53     ` Quentin Schulz
2026-03-25 16:26       ` Khem Raj
2026-03-25 16:35         ` Quentin Schulz
2026-03-25 14:45 ` Quentin Schulz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-11  8:25 Changqing Li
2026-03-11  9:15 ` [OE-core] " Alexander Kanavin
2026-03-12  1:05   ` Changqing Li
2026-03-18  2:12     ` Khem Raj
2026-03-18  2:21     ` Khem Raj

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=f4ed8844-38e7-49bb-9363-822af85f5012@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=changqing.li@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox