[bitbake-devel] nativesdk dependencies on shared packages
Oleksiy Obitotskyi -X (oobitots - GLOBALLOGIC INC at Cisco)
oobitots at cisco.com
Tue Oct 1 11:23:36 UTC 2019
Hi,
We have situation when MACHINE value change affect nativesdk packages (thud but the same situation was on krogoth).
MACHINE="x86" bitbake nativesdk-<package> -> build package and dependencies x86
MACHINE="x86-64" bitbake nativesdk-<package> -> build package and dependencies for x86-64
and finally
MACHINE="x86" bitbake nativesdk-<cpackage> -> a lot of setscene functons executed for nativesdk packages
MACHINE value affects BASELIB. For x86-64 we override BASELIB = lib64.
For x86 BASELIB = lib. baselib for cross/natviesdk ramains unchanged (lib).
# $BASELIB
# set <>/openembedded-core/meta/conf/bitbake.conf:12
# "lib"
# pre-expansion value:
# "lib"
BASELIB="lib"
# $BASELIB [2 operations]
# set <>/openembedded-core/meta/conf/bitbake.conf:12
# "lib"
# set <>/x86-64-platforms.inc:22
# "lib64"
# pre-expansion value:
# "lib64"
BASELIB="lib64"
Tracking dependencies shows that nativesdk-<package> depends on gcc-crosssdk which depend on
shared gcc-source package. And gcc-source tasks hash values (starting from from gcc-source.do_patch) are different for
x86 and x86-64 (due to baselib), so nativesdk-<package> task stamp signature deps part depends on gcc-source tasks hash
and also become different if we change MACHINE.
Technically it can be fixed with tweaking sstate_rundepfilter - but it's not generic solution.
Is there any way to avoid rebuilding nativesdk packages that depend on shared packages (e.g. gcc-source)?
Regards,
Oleksiy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/bitbake-devel/attachments/20191001/2c58da80/attachment.html>
More information about the bitbake-devel
mailing list