Re: [OE-core][PATCH] qemu: upgrade 10.2.0 -> 11.0.0

[Quan Sun <Quan.Sun@windriver.com>]

On 5/8/26 16:08, 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 Thu, 7 May 2026 at 22:29, Quan Sun <Quan.Sun@windriver.com> wrote:
>
>> When these subprojects are built standalone (outside the main QEMU meson
>> project), they fail to compile because they cannot find headers from the
>> top-level QEMU source tree (e.g. include/standard-headers/ or root-level
>> headers). In a normal upstream build, the parent project provides these
>> paths implicitly. OE's build environment triggers standalone subproject
>> builds, requiring explicit include paths.
> I'm afraid I don't understand, and I can't reproduce the issue. I
> deleted this patch from SRC_URI, and qemu-native, qemu-system-native
> and qemu (target) still build just fine.
>
> What kind of error are you observing? How can it be reproduced? What
> exactly triggers the 'standalone build' and how does it look like
> compared to 'normal upstream build'?

It's weird when I was working with the upgrade using the devtool, I 
clearly got build errors and that's why I added that patch. But as you 
said here, by removing that patch file, the build does succeed.   I've 
verified that the patch is not needed. The libvduse and libvhost-user 
subprojects are actually built as meson subprojects of the top-level 
QEMU build, not as standalone projects. I've tested qemu-native, 
qemu-system-native, and qemu (target) without this patch and all build 
successfully. So Dropping that patch file. Thanks a lot!