From: Changqing Li <changqing.li@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] mesa-tools-native: fix do_compile failure
Date: Thu, 12 Mar 2026 09:05:35 +0800 [thread overview]
Message-ID: <165ebb9c-7b39-4c96-b180-cb2e131312fc@windriver.com> (raw)
In-Reply-To: <CANNYZj-8T7fs-mnfXCA9AGZdt2J_uRrFQE0o9_szrXes5bez=w@mail.gmail.com>
On 3/11/26 17:15, Alexander Kanavin wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Wed, 11 Mar 2026 at 09:25, Changqing Li via lists.openembedded.org
> <changqing.li=windriver.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"
> This is not seen on the autobuilder, so what is the configuration that
> triggers it?
It is triggered when DISTRO_FEATURES contains opengl, but not contains
"x11 wayland". Now, poky enable opengl x11 wayland by default.
//Changqing
> Alex
next prev parent reply other threads:[~2026-03-12 1:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 8:25 [PATCH] mesa-tools-native: fix do_compile failure Changqing Li
2026-03-11 9:15 ` [OE-core] " Alexander Kanavin
2026-03-12 1:05 ` Changqing Li [this message]
2026-03-18 2:12 ` Khem Raj
2026-03-18 2:21 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2026-03-25 7:39 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
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=165ebb9c-7b39-4c96-b180-cb2e131312fc@windriver.com \
--to=changqing.li@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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