On Mon, 2020-08-17 at 10:15 -0400, Bruce Ashfield wrote: > > > On Mon, Aug 17, 2020 at 8:27 AM Richard Purdie < > richard.pur...@linuxfoundation.org> wrote: > > On Sun, 2020-08-16 at 18:55 -0400, Bruce Ashfield wrote: > > > > > > > > > On Sun, Aug 16, 2020 at 9:47 AM Richard Purdie < > > > richard.pur...@linuxfoundation.org> wrote: > > > > On Sat, 2020-08-15 at 19:41 -0700, Khem Raj wrote: > > > > > Bruce, > > > > > > > > > > We need > > > > > > > > > > > https://github.com/torvalds/linux/commit/168200b6d6ea0cb5765943ec5da5b8149701f36a > > > > > backported to 5.4 kernels for perf to build with -fno-common > > can > > > > you > > > > > queue this in your kernel updates as soon as you can ? > > > > > > > > I think we have other active kernels which will also need it as > > > > even > > > > with Khem's patch we still see failures: > > > > > > > > > > I've taken care of linux-yocto now, I don't think there are any > > > active use cases for those kernels that won't be covered. > > > > I bumped the meta-yocto BSPs with a quickly hacked up patch but we > > still see: > > > > I have local bumps for the yocto-bsps as well, let me try a perf > build against beaglebone to see if I can see anything. > > If I build master-next, will I get all the required gcc patches to > trigger the issue ?
You need: http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=c79101ffff8a9cc70daefe737e16b773190bb6ca without its revert (which is also in -next atm). Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#141567): https://lists.openembedded.org/g/openembedded-core/message/141567 Mute This Topic: https://lists.openembedded.org/mt/75983138/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
