<div dir="ltr">Please send whatever you currently have, so I can test it in my world build with more layers.<div><br></div><div>I've already included bitbake.conf change and e.g. pigz-native you listed here is already failing so I doubt the build with test any reasonable number of recipes if I let it run like this.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 5, 2016 at 6:32 PM, Mike Crowe <span dir="ltr"><<a href="mailto:mac@mcrowe.com" target="_blank">mac@mcrowe.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, 2016-02-02 at 14:49 +0000, Mike Crowe wrote:<br>
</span>> > > > [snip] Set EXTRA_OEMAKE = "" in bitbake.conf<br>
<span class=""><br>
On Tuesday 02 February 2016 at 16:01:14 +0000, Richard Purdie wrote:<br>
</span><span class="">> > > Which architectures did you test? Often, x86 is a bad choice here and<br>
> > > we'd need something cross (arm/mips/ppc) to ensure it really is doing<br>
> > > the right things. We also need to assess a bit more than just sato.<br>
> > > We can run this up on the autobuilder and see what happens.<br>
<br>
</span><span class="">On Tue, 2016-02-02 at 21:04 +0000, Mike Crowe wrote:<br>
</span><span class="">> > I've compile-tested qemux86 and qemuarm for core-image-sato. qemumips<br>
> > is building now.<br>
<br>
</span>Since then I've collected enough patches to make "bitbake world" build<br>
successfully for qemux86, qemuarm, qemuppc and qemumips. qemux86-64 is<br>
building now. The recipes that needed fixing to explicitly set<br>
EXTRA_OEMAKE = "-e MAKEFLAGS=" were:<br>
<br>
meta/recipes-bsp/apmd/<a href="http://apmd_3.2.2-15.bb" rel="noreferrer" target="_blank">apmd_3.2.2-15.bb</a><br>
meta/recipes-bsp/libacpi/<a href="http://libacpi_0.2.bb" rel="noreferrer" target="_blank">libacpi_0.2.bb</a><br>
meta/recipes-bsp/pciutils/<a href="http://pciutils_3.4.1.bb" rel="noreferrer" target="_blank">pciutils_3.4.1.bb</a><br>
meta/recipes-connectivity/openssl/openssl.inc<br>
meta/recipes-devtools/dmidecode/<a href="http://dmidecode_3.0.bb" rel="noreferrer" target="_blank">dmidecode_3.0.bb</a><br>
meta/recipes-devtools/fdisk/<a href="http://gptfdisk_1.0.1.bb" rel="noreferrer" target="_blank">gptfdisk_1.0.1.bb</a><br>
meta/recipes-devtools/perl/<a href="http://perl-native_5.22.1.bb" rel="noreferrer" target="_blank">perl-native_5.22.1.bb</a><br>
meta/recipes-devtools/perl/<a href="http://perl_5.22.1.bb" rel="noreferrer" target="_blank">perl_5.22.1.bb</a><br>
meta/recipes-extended/ed/<a href="http://ed_1.9.bb" rel="noreferrer" target="_blank">ed_1.9.bb</a><br>
meta/recipes-extended/iputils/<a href="http://iputils_s20151218.bb" rel="noreferrer" target="_blank">iputils_s20151218.bb</a><br>
meta/recipes-extended/pigz/pigz.inc<br>
meta/recipes-extended/stat/<a href="http://stat_3.3.bb" rel="noreferrer" target="_blank">stat_3.3.bb</a><br>
meta/recipes-extended/sysklogd/sysklogd.inc<br>
meta/recipes-extended/unzip/<a href="http://unzip_6.0.bb" rel="noreferrer" target="_blank">unzip_6.0.bb</a><br>
meta/recipes-gnome/gtk-theme-torturer/<a href="http://gtk-theme-torturer_git.bb" rel="noreferrer" target="_blank">gtk-theme-torturer_git.bb</a><br>
meta/recipes-support/ptest-runner/<a href="http://ptest-runner_2.0.bb" rel="noreferrer" target="_blank">ptest-runner_2.0.bb</a><br>
<br>
I will submit patches for these shortly.<br>
<span class=""><br>
> > We've been running with the previous version of the patch with our code<br>
> > for a while but now I look more closely that solution didn't have<br>
> > anywhere near as wide an impact so I'll switch us over to using these<br>
> > patches. That will runtime-test a few real mips and arm targets (and<br>
> > even x86 and x86-64 to a limited extent) but only with our customised<br>
> > set of packages.<br>
<br>
</span><span class="">On Tuesday 02 February 2016 at 22:41:25 +0000, Richard Purdie wrote:<br>
> Thanks. Please do mention what tests have passed/failed just so I can<br>
> build some idea of the risk of the patch and decide if/as/when the<br>
> right time to merge it is.<br>
<br>
</span>I've not yet done any more runtime tests. I hope to get the change into our<br>
tree tonight so everything gets rebuilt with it over the weekend and I can<br>
test next week.<br>
<span class=""><br>
> > > A post to the architecture list is probably needed so everyone knows<br>
> > > this is happening (or at least being considered).<br>
<br>
</span>I hope to send such a post later today.<br>
<span class="HOEnZb"><font color="#888888"><br>
Mike.<br>
</font></span></blockquote></div><br></div>