Build ncurses-native with target 'qemumips' and any other targets such as qemux86/qemuarm ..., compare the checksums of *ncurses-native* sstate files: --------------- qemumips: ----------------- cb/sstate-ncurses-native-x86_64-linux-5.9-r13.1-x86_64-3-cbad5187fc7ee0a9fcd27e2ac567f9dd_populate-sysroot.tgz cb/sstate-ncurses-native-x86_64-linux-5.9-r13.1-x86_64-3-cbad5187fc7ee0a9fcd27e2ac567f9dd_populate-sysroot.tgz.siginfo --------------- other targets: ------------ 87/sstate-ncurses-native-x86_64-linux-5.9-r13.1-x86_64-3-87e50121db82f29e77d4f02930e83f57_populate-sysroot.tgz 87/sstate-ncurses-native-x86_64-linux-5.9-r13.1-x86_64-3-87e50121db82f29e77d4f02930e83f57_populate-sysroot.tgz.siginfo This cause the native sstate files can't be re-used between mips and other archs. Analysis: ---------------- 1) This appears on the packages which inherit 'multilib_header', and those packages that depends on them: * ncurses-native * python-native * binutils-native * apr-native * beecrypt-native ... 2) There's some special code involved in mips causes the checksum difference: + MIPSPKGSFX_ABI = "${@bb.utils.contains("TUNE_FEATURES", "n32", "-n32", "", d)}" Maybe this is necessary for the target packages of mips, but it should not affect the native tools.
Created attachment 1045 [details] the output of bitbake-diffsigs to ncurses-native.do_install which the first task has different sifdata Attached the output of bitbake-diffsigs to ncurses-native-xxx.do_install.xxx which the first task has different sifdata.
(In reply to comment #1) > Created attachment 1045 [details] > the output of bitbake-diffsigs to ncurses-native.do_install which the first > task has different sifdata > > Attached the output of bitbake-diffsigs to ncurses-native-xxx.do_install.xxx > which the first task has different sifdata. s/sifdata/sigdata/
Patch out for review
Fixed in master: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=b15730caf0d4c40271796887505507f2501958bb