1938 2012-01-27 02:25:59 +0000 Detect Host system changes when using sstate 2012-10-05 11:04:23 +0000 1 1 7 Build System, Metadata & Runtime Meta-yocto meta-yocto unspecified x86 Multiple VERIFIED FIXED (P1)(Scheduled) Patches out for review Medium enhancement 1.3 M3 1 richard.purdie richard.purdie corneliux.stoicescu poky.bs.watcher poky.watcher song.liu --- --- --- oldest_to_newest 18394 0 richard.purdie 2012-01-27 02:25:59 +0000 If sstate packages are build on a system with a specific glibc version, there should be some way to detect when they're installed on an older system and at least flag the packages as invalid. Running against newer glibc shouldn't be an issues, its just a question on detecting and invalidating running on older glibc than the package was built for. 23523 1 richard.purdie 2012-07-26 13:20:56 +0000 For now, the best approach is going to be to mark sstate packages as being built against a given lsb_release name/version. There are patches our for review which do this. 23578 2 richard.purdie 2012-07-29 09:33:57 +0000 Fixed in master http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=72ab2866e1727c373c3c651f98b1e5b5f3d47e8f 26276 3 corneliux.stoicescu 2012-10-05 11:04:23 +0000 Verified in master, commit: ef5dcad3e3e3c004112cfc00843727a7fda75cd2 Changing distros will cause bitbake to make a new directory in sstate-chache with distro name and version in which to store its native and cross packages. Example: /build/sstate-cache/Ubuntu-12.04/*/sstate-*-native-*.tgz /build/sstate-cache/Ubuntu-12.04/*/sstate-*-cross-*.tgz