[OE-core] [PATCH 0/9] kernel-yocto: consolidated pull request

Bruce Ashfield bruce.ashfield at windriver.com
Tue Aug 22 15:34:58 UTC 2017


On 08/22/2017 11:28 AM, Richard Purdie wrote:
> On Tue, 2017-08-22 at 10:54 -0400, Bruce Ashfield wrote:
>> On 08/22/2017 10:24 AM, Richard Purdie wrote:
>>>   
>>> Thanks, I think you got that one but the /bin/awk issue remained
>>> after
>>> your changes. Its easy to reproduce with "bitbake core-image-sato-
>>> sdk",
>>> or IMAGE_INSTALL_append = " kernel-devsrc". I ended up with this
>>> change
>>> to fix it:
>> Yah, I noticed all of those references as well. Saul had dealt with
>> the one that hit us before, but I wasn't able to trigger any installs
>> of the other parts in the images I built .. so they were being left
>> be for now, just to keep our footprint low.
>>
>>>
>>>
>>> http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=
>>> a28acfa6c5890df4f5cb09962ef0c53837ac3b37
>>>
>>> which I appreciate you won't like but it illustrates the problem.
>>> Any
>>> preference on what to do with that patch?
>> I can merge it directly into linux-yocto, since that is what we did
>> with Saul's change before, and at the same time, we can submit it
>> upstream and drop it next release.
> 
> Ok, Should I merge my patch for now and you and then deal with it in
> due course or do you want to do that directly?

I can send you a v4 of the 4.12 patch in the next half an hour,
that's easiest for me to do.

.. but if it isn't for you, go ahead and do the merge and I'll
sort it out in a follow up.

> 
> I can take care of the mips issue but we have one final problem:
> 
> "oe-selftest -r runqemu.RunqemuTests.test_boot_machine_iso"
> 
> is failing, it works with 4.10, fails with 4.12. Did some key config
> option for booting isos go missing?

Not that I'm aware of, but I admit that I've never done any ISO
booting of the images so wouldn't see it.

I'll diff the configs here and see if anything jumps out. Otherwise,
I'll do a boot test myself and debug from there.

Bruce

> 
> Cheers,
> 
> Richard
> 




More information about the Openembedded-core mailing list