<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 6, 2017 at 11:28 AM, Burton, Ross <span dir="ltr"><<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.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">The amended commit has mismatching commit log and patch (target elfutils is in the commit log but not the patch), and doesn't mention installing target elfutils if they want it.</div></blockquote><div><br></div><div><br></div><div>I fixed up the commit log on that patch to match the actual code.</div><div><br></div><div>As it turns out, I don't see the need to install target elfutils anymore, so I didn't</div><div>include anything about that in the log.</div><div><br></div><div>We still have some lttng build issues with the -dev kernel (due to objtool being</div><div>required and the openssl headers required for making the scripts), and those</div><div>are being worked on separately. Having this updated linux-yocto-dev recipe</div><div>in the tree gets the kernel building and booting and enables us to work through</div><div>the other issues more quickly (not to meention, I've already pushed 4.15-rc2 to</div><div>the actual kernel tree, so you get that from a build regardless).</div><div><br></div><div>Cheers,</div><div><br></div><div>Bruc</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class="HOEnZb"><font color="#888888"><div><br></div><div>Ross</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 4 December 2017 at 17:43, Bruce Ashfield <span dir="ltr"><<a href="mailto:bruce.ashfield@windriver.com" target="_blank">bruce.ashfield@windriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 2017-12-04 12:39 PM, Richard Purdie wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, 2017-12-04 at 12:24 -0500, Bruce Ashfield wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 2017-12-04 11:38 AM, Khem Raj wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On Mon, Dec 4, 2017 at 7:39 AM, Bruce Ashfield<br>
<<a href="mailto:bruce.ashfield@windriver.com" target="_blank">bruce.ashfield@windriver.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Outside of the normal patch refreshes and boot issues, there are<br>
new<br>
build time tools within the kernel that required the following<br>
dependencies:<br>
<br>
For ORC_UNWINDER support in x86-64:<br>
<br>
DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-<br>
native elfutils', '', d)}"<br>
</blockquote>
do we need both target and host elfutils<br>
</blockquote>
Yup. There were references to both. Some had to run for hostcc<br>
and others in the target arch.<br>
</blockquote>
<br>
Just for reference this is pretty bad for performance as it delays the<br>
kernel compile until some substantial parts of userspace build.<br>
<br>
</blockquote>
<br></span>
On a second look, I can likely turn off the target part, if someone<br>
wants it, they can always install the package (or it could be a<br>
rdepends).<br>
<br>
I'll amend the commit and leave it on that branch with just the<br>
DEPENDS on the -native version.<span><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is ORC_UNWINDER useful and commonly used?<br>
</blockquote>
<br></span>
The upstream kernel commit turned it on by default, I turned it off in<br>
the kernel-cache, but I wanted to make sure the dependency was<br>
in place.<br>
<br>
The commit series from Josh Poimboeuf all lead to it being on as<br>
the default choice (even with a slight overhead).<span class="m_-1893885360894538066HOEnZb"><font color="#888888"><br>
<br>
Bruce</font></span><div class="m_-1893885360894538066HOEnZb"><div class="m_-1893885360894538066h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Cheers,<br>
<br>
Richard<br>
<br>
</blockquote>
<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></div><br></div>
</div></div><br>--<br>
______________________________<wbr>_________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.<wbr>openembedded.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>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"</div>
</div></div>