On Wed, 2019-06-19 at 07:45 -0700, akuster808 wrote: > > On 6/19/19 6:56 AM, Richard Purdie wrote: > > This avoids sstate/uninative relocation issues where a binary was > > built against > > a system with libcrypt.so.1 or libcrypt.so.2 and then run on the > > opposite by > > ensuring both libraries are in uninative. > Does this affect stable branches?
Yes, we'll need to upgrade to the new uninative release, assuming these patches test successfully, merge and we make a new release with these tweaks in. I was going to send you email about this. I've cc'd Vineela+Tracy so they know too as I'd planned to give them a headsup. [Context is autobuilder failures with this issue which I root caused, SWAT hasn't filed the bug yet so we're ahead of them!] Cheers, Richard -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
