<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 21, 2017 at 8:11 AM, Bruce Ashfield <span dir="ltr"><<a href="mailto:bruce.ashfield@gmail.com" target="_blank">bruce.ashfield@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_2276324336682558043h5">On Mon, Aug 21, 2017 at 7:42 AM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundatio<wbr>n.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="m_2276324336682558043m_-9070533304822977223HOEnZb"><div class="m_2276324336682558043m_-9070533304822977223h5">On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:<br>
> Hi all,<br>
><br>
> Here's the collected set of kernel changes that are ready for the M3<br>
> builds.<br>
><br>
> We have some kernel meta data changes:<br>
><br>
> kernel-yocto: configuration updates: x86 features<br>
> linux-yocto/4.1: fix fsl-ls10xx sdhci<br>
> linux-yocto: add usb-net configs by default<br>
><br>
> Some bug fixes:<br>
><br>
> kernel-yocto: ensure that only valid BSPs are built<br>
> linux-yocto/4.10: CVE & misc fixes<br>
><br>
> And the important changes are the addition of the 4.12 kernel + libc<br>
> headers<br>
> and the removal of the 4.1 kernel.<br>
><br>
> I also have some -stable updates queued for the active kernel<br>
> versions, but<br>
> they will come out once this series has made it into the tree, since<br>
> I'm<br>
> trying to isolate any 4.12 issues from other -stable updates.<br>
><br>
> I built and booted all the qemu targets for 4.12, and have built for<br>
> core-image-sato, core-image-kernel-dev, glibc and muslc for all of<br>
> the<br>
> architectures. My testing didn't pick up any regressions, but I was<br>
> battling<br>
> some other build errors (non kernel related) during my testing, so I<br>
> can<br>
> never be 100% sure.<br>
><br>
> I've sent patches to poky to remove/bump any references to the 4.1<br>
> kernel<br>
> .. if I've missed any, I'm sure people will shout.<br>
<br>
</div></div>I added an extra patch for the ones you missed in meta-yocto-bsp ;-)<br>
<br>
Also, <a href="https://autobuilder.yocto.io/builders/build-appliance/builds/425/steps/BuildImages_1/logs/stdio" rel="noreferrer" target="_blank">https://autobuilder.yoct<wbr>o.io/builders/build-appliance/<wbr>builds/425/<br>
steps/BuildImages_1/logs/stdio</a><br>
<br>
Error: <br>
Problem: conflicting requests<br>
- nothing provides /bin/awk needed by kernel-devsrc-1.0-r0.0.qemux86<wbr>_64<br></blockquote><div><br></div></div></div><div>Hmm. I've built that exact combination on two different builders in the past week</div><div>and have never seen this.</div><div><br></div><div>How do I find out about the environment on that machine ? Because I'm not going</div><div>to be able to reproduce it here.</div></div></div></div></blockquote><div><br></div><div>A little bit more information. Saul fixed this earlier this year, and I'm still carrying</div><div>a patch that ensures that /usr/bin/awk is in the ver_linux script instead of /bin/awk.</div><div>That fix used to satisfy a similar requirement.</div><div><br></div><div>That being said, I did notice that Saul's change was accepted upstream and the</div><div>patch I'm carrying is not correctly applied (but it should be an invalid patch, not</div><div>a reference to /bin/awk).</div><div><br></div><div>I've fixed that patch, and am building the build-appliance image now.</div><div><br></div><div>I will have a new set of SRCREVs for linux-yocto-4.12, but I can't say if they'll</div><div>fix the particular issue that the autobuilder is seeing.</div><div><br></div><div>Bruce</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>Bruce</div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Cheers,<br>
<br>
Richard<br>
<div class="m_2276324336682558043m_-9070533304822977223HOEnZb"><div class="m_2276324336682558043m_-9070533304822977223h5"><br>
<br>
--<br>
______________________________<wbr>_________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openem<wbr>bedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>core</a><br>
</div></div></blockquote></span></div><span class="m_2276324336682558043HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div class="m_2276324336682558043m_-9070533304822977223gmail_signature" data-smartmail="gmail_signature">"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"</div>
</font></span></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="m_2276324336682558043gmail_signature" data-smartmail="gmail_signature">"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"</div>
</div></div>