Re: [OE-core] [PATCH] feature-arm-neon.inc: restore vfpv3-d16 support

On Thu, May 12, 2016 at 2:51 AM, André Draszik wrote: > OK. Any suggestions for how to best fix that? > > I could be more specific and .replace('vfpv3-d16', 'vfpv3d16') only, but > that seems ugly :-) There seem to be no other usecase where '-' is used in fpu names so it should

Re: [OE-core] [PATCH] feature-arm-neon.inc: restore vfpv3-d16 support

OK. Any suggestions for how to best fix that? I could be more specific and .replace('vfpv3-d16', 'vfpv3d16') only, but that seems ugly :-) Thanks, André On Mi, 2016-05-11 at 11:55 -0700, Khem Raj wrote: > This causes raspberrypi2 not parse anymore > > ERROR:  OE-core's config sanity checker

Re: [OE-core] [PATCH] feature-arm-neon.inc: restore vfpv3-d16 support

This causes raspberrypi2 not parse anymore ERROR: OE-core's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: Error,

[OE-core] [PATCH] feature-arm-neon.inc: restore vfpv3-d16 support

Commit 6661718 (feature-arm-{neon,vfp}.inc: refactor and fix issues) effectively changed the gcc -mfpu= option from -mfpu=vfpv3-d16 to -mfpu=vfpv3d16, which gcc doesn't understand. Restore the original value. After doing that, we also need to adjust ARMPKGSFX_FPU which should contain the same