On Mon, Aug 19, 2019 at 7:31 AM Ross Burton <ross.bur...@intel.com> wrote:
> On 14/08/2019 23:46, Khem Raj wrote: > > On Wed, Aug 14, 2019 at 3:42 PM akuster808 <akuster...@gmail.com> wrote: > >> > >> > >> > >> On 8/14/19 3:29 PM, Khem Raj wrote: > >>> libffi 3.1 release has been a bit aged and new architectures, compilers > >>> have since been come on stage to compile it, we have been carrying > >>> patches, but its better to use the latest 3.3 rc0 which has lot of > these > >>> issues handled and is in good shape. > >> > >> Will the RC part cause the PE to be invoked when 3.3 comes out? I did > >> this on wireshark and shot myself in the foot. > >> > > > > I am expecting the releases to be 3.3.0 but looking into the history > > of releases it > > could be 3.3 so yes you are right, Probably I will renable the recipe > > to libffi_3.2+3.3-rc0.bb > > and that should fix this > > Set the PV to 3.3~rc0 and 3.3 will sort after it. I thinking using + terminology is familiar in OE world let’s stick to it > > > Ross > > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core >
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
