<div dir="ltr">The patch is "uninative: rebuild uninative for gcc 4.8 and 4.9" but I forgot it didn't get merged as it broke eSDK.<div><br></div><div>Ross</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 9 December 2016 at 16:23, Aníbal Limón <span dir="ltr"><<a href="mailto:anibal.limon@linux.intel.com" target="_blank">anibal.limon@linux.intel.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=""><br>
<br>
On 12/08/2016 02:35 PM, Burton, Ross wrote:<br>
> On 8 December 2016 at 19:16, Andre McCurdy <<a href="mailto:armccurdy@gmail.com">armccurdy@gmail.com</a>> wrote:<br>
><br>
>> Is it correct that native sstate from a host with gcc < 4.9 should be<br>
>> reused by a host with gcc >= 4.9 ?<br>
>><br>
>> Doesn't the change in NATIVELSBSTRING prevent that from happening?<br>
>><br>
><br>
> Yes, we recently landed a change so that uninative is versioned by host<br>
> GCC. Presumably that solves this problem in a different way?<br>
<br>
</span>If the sstate generated is different from a host distro with gcc>=4.9<br>
and gcc<4.9 will be work.<br>
<br>
Could you point me to the patch that makes this change?<br>
<br>
alimon<br>
<br>
><br>
> Ross<br>
><br>
<br>
</blockquote></div><br></div>