On Mon, Aug 17, 2020 at 3:55 PM Khem Raj <raj.k...@gmail.com> wrote: > On Mon, Aug 17, 2020 at 12:47 PM Khem Raj <raj.k...@gmail.com> wrote: > > > > On Mon, Aug 17, 2020 at 5: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: > > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/2339 > > > > > > so I think there may be another patch we need somewhere... > > > > > > (which matches what we saw with Khem's _append which also failed). > > > > > > > there seems to be concaternation of compiler options without space > > > > | arm-poky-linux-gnueabi-gcc: error: unrecognized argument in option > > '-mfpu=neon/include/uapi/asm-generic/errno.h' > > | arm-poky-linux-gnueabi-gcc: note: valid arguments to '-mfpu=' are: > > auto crypto-neon-fp-armv8 fp-armv8 fpv4-sp-d16 fpv5-d16 fpv5-sp-d16 > > neon neon-fp-armv8 neon-fp16 neon-vfpv3 neon-vfpv4 vfp vfp3 vfpv2 > > vfpv3 vfpv3-d16 vfpv3-d16-fp16 vfpv3-fp16 vfpv3xd vfpv3xd-fp16 vfpv4 > > vfpv4-d16 > > | arm-poky-linux-gnueabi-gcc: fatal error: no input files > > > > but it also showed up on x86_64 in one of your prior builds, so I > > wonder if its something in kernel build system or is it processing > > TUNE_CCARGS in special ways. > > > > > There is still some piece of this we're missing, maybe on non-IA. > > > > > Perhaps these kernel backports might help > > > https://github.com/torvalds/linux/commit/7597ce89b3ed239f7a3408b930d2a6c7a4c938a1 > > https://github.com/torvalds/linux/commit/6d1f916265aa615218d341ba5d3fd39dfe931cde
I unfortunately had to clean and rebuild my development machine, so only now started a reference h/w build to see what's up with perf. I'll follow up tomorrow when I have some input. Cheers, Bruce > > > > > Cheers, > > > > > > Richard > > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#141582): https://lists.openembedded.org/g/openembedded-core/message/141582 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] -=-=-=-=-=-=-=-=-=-=-=-
