QEMU native compile issue
Brad Bishop
bradleyb at fuzziesquirrel.com
Mon Sep 9 21:57:13 AEST 2019
at 8:08 PM, Andrew Jeffery <andrew at aj.id.au> wrote:
> On Wed, 28 Aug 2019, at 00:09, Johnathan Mantey wrote:
>> Not really. I'm not sure where the code went.
>>
>> I cloned the OpenBMC QEMU, made my change, and then pushed the change
>> to "upstream". I have SHA "650af0e183 Fix compile error when using
>> kernel 5.2" as the text.
>
> As you noted in your follow-up email you found the fix upstream. Further,
> the fix
> is contained in the QEMU v4.1 tag.
>
> Upstream open-embedded has already bumped QEMU to v4.1 - I guess we
> should backport that change to openbmc/openbmc and this will be resolved.
> I've Cc'ed Brad so he's across it.
I think this was picked up with openbmc
c68388fccb8c0b5bf4d6b8efff91203796be98b2.
If that doesn’t have what we needed...I’m blocked on doing further oe-core
updates because of this:
https://lists.ozlabs.org/pipermail/openbmc/2019-September/017984.html
-brad
More information about the openbmc
mailing list