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

Bruce Ashfield bruce.ashfield at gmail.com
Mon Aug 21 12:11:55 UTC 2017


On Mon, Aug 21, 2017 at 7:42 AM, Richard Purdie <
richard.purdie at linuxfoundation.org> wrote:

> On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
> > Hi all,
> >
> > Here's the collected set of kernel changes that are ready for the M3
> > builds.
> >
> > We have some kernel meta data changes:
> >
> >   kernel-yocto: configuration updates: x86 features
> >   linux-yocto/4.1: fix fsl-ls10xx sdhci
> >   linux-yocto: add usb-net configs by default
> >
> > Some bug fixes:
> >
> >   kernel-yocto: ensure that only valid BSPs are built
> >   linux-yocto/4.10: CVE & misc fixes
> >
> > And the important changes are the addition of the 4.12 kernel + libc
> > headers
> > and the removal of the 4.1 kernel.
> >
> > I also have some -stable updates queued for the active kernel
> > versions, but
> > they will come out once this series has made it into the tree, since
> > I'm
> > trying to isolate any 4.12 issues from other -stable updates.
> >
> > I built and booted all the qemu targets for 4.12, and have built for
> > core-image-sato, core-image-kernel-dev, glibc and muslc for all of
> > the
> > architectures. My testing didn't pick up any regressions, but I was
> > battling
> > some other build errors (non kernel related) during my testing, so I
> > can
> > never be 100% sure.
> >
> > I've sent patches to poky to remove/bump any references to the 4.1
> > kernel
> > .. if I've missed any, I'm sure people will shout.
>
> I added an extra patch for the ones you missed in meta-yocto-bsp ;-)
>
> Also, https://autobuilder.yocto.io/builders/build-appliance/builds/425/
> steps/BuildImages_1/logs/stdio
>
> Error:
>  Problem: conflicting requests
>   - nothing provides /bin/awk needed by kernel-devsrc-1.0-r0.0.qemux86_64
>

Hmm. I've built that exact combination on two different builders in the
past week
and have never seen this.

How do I find out about the environment on that machine ? Because I'm not
going
to be able to reproduce it here.

Bruce


>
> Cheers,
>
> Richard
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170821/a234d794/attachment-0002.html>


More information about the Openembedded-core mailing list