From: Rasmus Villemoes <ravi@prevas.dk>
To: Denys Dmytriyenko <denis@denix.org>
Cc: Ryan Eatmon <reatmon@ti.com>, <meta-ti@lists.yoctoproject.org>
Subject: Re: [meta-ti] [PATCH] mesa-pvr: correct INSANE_SKIP for mesa-megadriver
Date: Tue, 28 Jul 2026 10:59:32 +0200 [thread overview]
Message-ID: <87h5lja3rf.fsf@prevas.dk> (raw)
In-Reply-To: <20260720155303.GO10186@denix.org> (Denys Dmytriyenko's message of "Mon, 20 Jul 2026 11:53:03 -0400")
On Mon, Jul 20 2026, Denys Dmytriyenko <denis@denix.org> wrote:
> On Mon, Jul 20, 2026 at 09:14:42AM +0200, Rasmus Villemoes via lists.yoctoproject.org wrote:
>> On Fri, Jul 17 2026, Ryan Eatmon <reatmon@ti.com> wrote:
>>
>> > On 7/17/2026 7:48 AM, Rasmus Villemoes via lists.yoctoproject.org wrote:
>> >> In the original file this was copied from, $PN == mesa. But in this
>> >> context, $PN == mesa-pvr, while the PACKAGES and FILES logic still
>> >> explicitly refers to the mesa-megadriver package. Hence the build
>> >> fails
>> >>
>> >
>> > Good catch. I wonder why we are not seeing these QA errors in our
>> > builds. Are you turning something special on?
>>
>> No, not that I know of. I hit this immediately when trying to update
>> from whinlatter to wrynose, but I don't think we have any special flags
>> set anywhere that should increase bitbake warning/pedantic level or
>> something like that.
>
> It's not about warning or pedantic level. It's rather about how you have
> mesa and the entire distro configured. Because we don't have any of those
> 4 libraries in /usr/lib/dri/ being built, as we only build for Wayland, but
> not X11.
>
> PACKAGECONFIG="gallium video-codecs vulkan wayland opengl egl gles gbm virgl opencl libclc gallium-llvm zink xmlconfig gallium-llvm"
> DISTRO_FEATURES="pam opencl systemd usrmerge 3g acl alsa bluetooth debuginfod ext2 gobject-introspection-data ipv4 ipv6 ldconfig multiarch nfc nfs opengl pci pulseaudio seccomp vfat vulkan wayland wifi xattr zeroconf"
> DISTRO_FEATURES_OPTED_OUT="ptest x11"
>
> Might want to compare these to your settings.
>
> Anyway, your fix is correct - this is just an explanation for why we are not
> seeing the error in our builds.
Thanks.
Any chance this could be applied/backported to wrynose?
Rasmus
prev parent reply other threads:[~2026-07-28 8:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 12:48 [PATCH] mesa-pvr: correct INSANE_SKIP for mesa-megadriver Rasmus Villemoes
2026-07-17 13:08 ` PRC Automation
2026-07-17 14:09 ` [meta-ti] " Ryan Eatmon
2026-07-20 7:14 ` Rasmus Villemoes
2026-07-20 15:53 ` Denys Dmytriyenko
2026-07-28 8:59 ` Rasmus Villemoes [this message]
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=87h5lja3rf.fsf@prevas.dk \
--to=ravi@prevas.dk \
--cc=denis@denix.org \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@ti.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