summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/gcc/gcc-5.3.inc
diff options
context:
space:
mode:
authorRandy Witt <randy.e.witt@linux.intel.com>2016-05-01 17:13:02 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-05-11 10:33:42 +0100
commit47c994fff0444c984659e31cf7136b036f2e33f0 (patch)
tree43840cd4d2a3a292924c1f08e955d8b972c2d7c9 /meta/recipes-devtools/gcc/gcc-5.3.inc
parent1e88c74650a2c860180e780527672385e217d933 (diff)
downloadpoky-47c994fff0444c984659e31cf7136b036f2e33f0.tar.gz
populate_sdk_ext: Change lockedsigs task mismatch to a warning
It has been determined that it is highly likely that users might get signatures that don't match in an extensible sdk. This doesn't necessarily happen with oe-core, so we can set the mismatch to an error during testing if we like. However, for the case where users are creating their own sdks, we don't need an error halting their progress. locked-sigs will still function as it should. (From OE-Core rev: 6ba86d847275126bf435f144e7d029d10e7ab17d) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/gcc/gcc-5.3.inc')
0 files changed, 0 insertions, 0 deletions