On Mon, Aug 21, 2017 at 8:11 AM, Bruce Ashfield <bruce.ashfi...@gmail.com> wrote:
> > > On Mon, Aug 21, 2017 at 7:42 AM, Richard Purdie < > richard.pur...@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 >> <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. > A little bit more information. Saul fixed this earlier this year, and I'm still carrying a patch that ensures that /usr/bin/awk is in the ver_linux script instead of /bin/awk. That fix used to satisfy a similar requirement. That being said, I did notice that Saul's change was accepted upstream and the patch I'm carrying is not correctly applied (but it should be an invalid patch, not a reference to /bin/awk). I've fixed that patch, and am building the build-appliance image now. I will have a new set of SRCREVs for linux-yocto-4.12, but I can't say if they'll fix the particular issue that the autobuilder is seeing. Bruce > > Bruce > > >> >> Cheers, >> >> Richard >> >> >> -- >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@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" > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
