<div dir="ltr">See:<div><br></div><div><a href="http://lists.openembedded.org/pipermail/openembedded-core/2015-November/112919.html">http://lists.openembedded.org/pipermail/openembedded-core/2015-November/112919.html</a><br></div><div><br></div><div>I think it fixes the same issue.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 6, 2015 at 6:09 PM, Matt Madison <span dir="ltr"><<a href="mailto:matt@madison.systems" target="_blank">matt@madison.systems</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I was trying some multilib ARM builds and ran into an issue. For<br>
armv7ahf-neon-vfpv4, PACKAGE_EXTRA_ARCHS is coded as "armv7ahf-vfp-neon-vfpv4",<br>
but the ARMPKGSFX_FPU suffix was getting constructed as "-vfp-vfpv4-neon", resulting<br>
in 32-bit packages not getting found due to the name mismatch.<br>
<br>
The following patch fixes this by changing ARMPKGSFX_FPU. I'm not sure if it<br>
would be more correct to change the PACKAGE_EXTRA_ARCHS settings, but the<br>
'neon-vfpv4' more closely aligns to the tune names, so I took this route.<br>
<br>
Matt Madison (1):<br>
feature-arm-neon.inc, feature-arm-vfp.inc: fix vfpv4 suffix ordering<br>
<br>
meta/conf/machine/include/arm/feature-arm-neon.inc | 2 +-<br>
meta/conf/machine/include/arm/feature-arm-vfp.inc | 2 +-<br>
2 files changed, 2 insertions(+), 2 deletions(-)<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
2.5.0<br>
<br>
--<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</font></span></blockquote></div><br></div>