<div><div dir="auto"><br></div></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 19, 2019 at 7:31 AM Ross Burton <<a href="mailto:ross.burton@intel.com">ross.burton@intel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 14/08/2019 23:46, Khem Raj wrote:<br>
> On Wed, Aug 14, 2019 at 3:42 PM akuster808 <<a href="mailto:akuster808@gmail.com" target="_blank">akuster808@gmail.com</a>> wrote:<br>
>><br>
>><br>
>><br>
>> On 8/14/19 3:29 PM, Khem Raj wrote:<br>
>>> libffi 3.1 release has been a bit aged and new architectures, compilers<br>
>>> have since been come on stage to compile it, we have been carrying<br>
>>> patches, but its better to use the latest 3.3 rc0 which has lot of these<br>
>>> issues handled and is in good shape.<br>
>><br>
>> Will the RC part cause the PE to be invoked when 3.3 comes out? I did<br>
>> this on wireshark and shot myself in the foot.<br>
>><br>
> <br>
> I am expecting the releases to be 3.3.0 but looking into the history<br>
> of releases it<br>
> could be 3.3 so yes you are right, Probably I will renable the recipe<br>
> to libffi_3.2+<a href="http://3.3-rc0.bb" rel="noreferrer" target="_blank">3.3-rc0.bb</a><br>
> and that should fix this<br>
<br>
Set the PV to 3.3~rc0 and 3.3 will sort after it.</blockquote><div dir="auto"><br></div><div dir="auto">I thinking using + terminology is familiar in OE world let’s stick to it </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
Ross<br>
<br>
-- <br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">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>
</blockquote></div></div>