Because few people already asked:
if your shr-core build fails like this:
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:
Your configuration is using stamp files including the sstate hash but your
build directory was built with stamp files that do not include this.
To continue, either rebuild or switch back to the OEBasic signature handler
with BB_SIGNATURE_HANDLER = 'OEBasic'.
ERROR: Execution of event handler 'check_sanity_eventhandler' failed
ERROR: Command execution failed: Exited with
and you're not willing to rebuild from scratch, then it's quite safe
to update meta-smartphone for this commit (you probably have this already)
http://git.shr-project.org/git/?p=meta-smartphone.git;a=commit;h=fc433f7dc3945f6c602ccac9b4722d23171707c1
and
echo 8 > shr-core/tmp-eglibc/abi_version
if you're not using SHR makefile, then also update your bblayers.conf like this:
http://git.shr-project.org/git/?p=shr-makefile.git;a=commit;h=f692c25df1da55c6c43a8a59eaa4bd3978f42694
Cheers,
--
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
_______________________________________________ Shr-devel mailing list Shr-devel@lists.shr-project.org http://lists.shr-project.org/mailman/listinfo/shr-devel
