Bug 12586 - yocto-check-layer fails signatures due to TUNES between ARM archs
Summary: yocto-check-layer fails signatures due to TUNES between ARM archs
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.7 M1
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-03-06 17:29 UTC by Denys Dmytriyenko
Modified: 2018-11-09 15:24 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Log file (8.01 KB, text/plain)
2018-03-06 17:29 UTC, Denys Dmytriyenko 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Denys Dmytriyenko 2018-03-06 17:29:13 UTC 
Created attachment 4224 [details]
Log file

While running yocto-check-layers script on a BSP layer, it seems to not handle TUNES differences between ARMv7 and ARMv5 machines.

For illustration purposes, let's do qemuarm from oe-core vs. beaglebone-yocto from meta-yocto-bsp, but it extends to other ARM-based BSPs.

It fails in go-cross-arm with this error:

Variable DEFAULTTUNE value changed from 'armv5te' to 'cortexa8hf-neon'


Granted, beaglebone-yocto sets DEFAULTTUNE to cortexa8hf-neon, but it fails exactly the same when using standard DEFAULTTUNE of armv7athf-neon.

Full log is attached.
Comment 1 Armin Kuster 2018-04-19 08:30:01 UTC 
I heard we are seening something similar with x86 tunes.
Comment 2 Richard Purdie 2018-10-30 17:40:35 UTC 
The command to reproduce:

$ yocto-check-layer ../meta-yocto-bsp/ --machines qemuarm beaglebone-yocto

confirmed as still present on 2.6 rc1
Comment 4 Richard Purdie 2018-11-09 15:24:19 UTC 
Filed https://bugzilla.yoctoproject.org/show_bug.cgi?id=13004 to work on improving the --machines option.