Not to be fixed
Created: Nov 1, 2016
Updated: Mar 6, 2019
Resolved Date: Feb 20, 2019
Found In Version: unknown
Severity: Standard
Applicable for: Wind River Linux 9
Component/s: Build & Config
This only happens when install eSDK, can't reproduce it after eSDK is installed and run "bitbake linux-windriver -ccleansstate && bitbake linux-windriver", I've compared the signatures before the build and after, they are the same, it doesn't impact the usage of eSDK AFAIK.
$ bitbake -c populate_sdk_ext wrlinux-image-glibc-core
$ ./tmp/deploy/sdk/wrlinux-9.0.0.0-glibc-x86_64-qemuarm64-wrlinux-image-glibc-core-sdk-ext.sh
WARNING: The linux-windriver:do_compile sig is computed to be 52a115f24a99606c808546226a820ae2, but the sig is locked to 7edec5ee2070a8b8990a5f0f7158498b in SIGGEN_LOCKEDSIGS_t-qemuarm64
The linux-windriver:do_compile_kernelmodules sig is computed to be fa88f16aea96c709c9762a4a02089d6b, but the sig is locked to 84f0a7be67bdc512b9e6ce8d2bc4febf in SIGGEN_LOCKEDSIGS_t-qemuarm64
