Fixed
Created: Sep 19, 2016
Updated: Dec 3, 2018
Resolved Date: Mar 3, 2017
Found In Version: 8.0.0.8
Fix Version: 8.0.0.15
Severity: Standard
Applicable for: Wind River Linux 8
Component/s: Toolchain
Why is the WRL 8 version of the gcc-runtime MACHINE dependent?
In wr-sdk-toolchain/recipes-devtools/gcc/gcc-wr-common.inc, there is:
EXTRA_OECONF_append = " --with-pkgversion='${DISTRO_NAME} ${PV}-${SDK_VERSION}' --with-bugurl='support@windriver.com'"
SDK_VERSION contains MACHINE
This means that the gcc-runtime package is MACHINE dependant.
But it is not marked as a MACHINE_ARCH package.
Now, I would argue that the toolchain should _not_ be MACHINE dependant, as that will make it very hard to share multiple MACHINEs with the same ARCH.
As it is right now in wrl8, the gcc-runtime will be rebuild for each different MACHINE, although it is _not_ marked as MACHINE_ARCH,
Can we remove that MACHINE dependency? It break sstate sharing badly. (We would like to get the shared workspace feature working as we have a lot of things shared between different builds)
And as far as I know all package that is in fact dependant on MACHINE, should be marked as such with MACHINE_ARCH. (Although in this case I would argue that the MACHINE dependency should be removed instead.)
Is this done as this by choice, or is it a mistake that can be fixed?
