From: Quentin Schulz <quentin.schulz@cherry.de>
To: raj.khem@gmail.com, Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Changqing Li <changqing.li@windriver.com>
Subject: Re: [OE-core] [PATCH] mesa-tools-native: fix do_compile failure
Date: Wed, 25 Mar 2026 15:53:51 +0100 [thread overview]
Message-ID: <2169b9ae-3e23-47b8-94cd-09f985f8c8e3@cherry.de> (raw)
In-Reply-To: <CAMKF1soXSQxLU3eRCejvHH5HORG9xRMxObU+svnAdd10JAs37Q@mail.gmail.com>
Hi Khem,
On 3/25/26 3:46 PM, Khem Raj via lists.openembedded.org wrote:
> On Wed, Mar 25, 2026 at 5:52 AM Alexander Kanavin <alex.kanavin@gmail.com>
> wrote:
>
>> On Wed, 25 Mar 2026 at 08:40, Khem Raj via lists.openembedded.org
>> <raj.khem=gmail.com@lists.openembedded.org> wrote:
>>> 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
>>
>>> -DEPENDS += "libclc-native spirv-tools-native
>> spirv-llvm-translator-native"
>>> +DEPENDS += "libclc-native spirv-tools-native
>> spirv-llvm-translator-native libdrm-native"
>>
>> Should this be in PACKAGECONFIG for panfrost?
>>
>
> I have opengl-only image to build for odroid-c4 which does not have
> panfrost.
>
It "has", due to building mesa-tools-native which enables building
panfrost tools unconditionally.
panfrost PACKAGECONFIG may enable building the gallium driver (if
combined with gallium PACKAGECONFIG), the vulkan (panvk) driver (if
combined with vulkan PACKAGECONFIG) and/or the panfrost tools (if
combined with tools PACKAGECONFIG).
So it's a missing dependency for the panfrost tools and should be added
as dependency to the panfrost tools (see my other mail). I don't think
you need it if you're not building the panfrost tools.
Cheers,
Quentin
next prev parent reply other threads:[~2026-03-25 14:54 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 [this message]
2026-03-25 16:26 ` Khem Raj
2026-03-25 16:35 ` Quentin Schulz
2026-03-25 14:45 ` Quentin Schulz
-- 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=2169b9ae-3e23-47b8-94cd-09f985f8c8e3@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=alex.kanavin@gmail.com \
--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