summaryrefslogtreecommitdiffstats
path: root/scripts/oe-publish-sdk
diff options
context:
space:
mode:
authorRoss Burton <ross.burton@intel.com>2017-01-25 17:13:40 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-01-31 14:43:00 +0000
commite286829fcc4f99d23a278d3d34121f794296059e (patch)
treef9cfe3dcb7013ef1856ca741b50b5555f0018141 /scripts/oe-publish-sdk
parent9533e14e6ff8be13b5a3e156b1e738f986c026e8 (diff)
downloadpoky-e286829fcc4f99d23a278d3d34121f794296059e.tar.gz
package_deb: handle allarch when mapping tune to dpkg architectures
It was discovered that buildtools-tarball can't be built with Debian packaging: E: Unable to locate package nativesdk-buildtools-perl-dummy The package exists but dpkg doesn't see it because the Architecture field isn't valid: for this package the Architecture field is 'allarch' which isn't in the list of valid architectures we define. package_deb already has a mapping of OE architectures (PACKAGE_ARCH) to dpkg architectures (DPKG_ARCH), for example our x86_64 is amd64 in dpkg. However allarch.bbclass sets an invalid TARGET_ARCH of 'allarch' (to break anything which attempts to use the target architecture) and package_deb relied on the PACKAGE_ARCH check later turning the Architecture field into 'all'. This usually works, but nativesdk-buildtools-perl-dummy inherits allarch but then changes PACKAGE_ARCH to buildtools-dummy-nativesdk to isolate the packages in a separate feed. We can handle this by explictly checking for allarch in the TARGET_ARCH check, as that everything that inherits allarch will want to have Architecture: all in their packages. [ YOCTO #10700 ] (From OE-Core rev: 58a5771f20f7851816b5f39df0ada8f16438065c) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/oe-publish-sdk')
0 files changed, 0 insertions, 0 deletions