diff options
| author | Mark Hatle <mark.hatle@windriver.com> | 2015-01-15 09:05:33 -0600 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-01-21 14:28:48 +0000 |
| commit | 3e4d84aea3623d4eac2e5a094cf103b26859a6b6 (patch) | |
| tree | 57cd9bcd065b4dfd7fadc09f0271413b7df08e69 /meta/conf | |
| parent | 3290dc9e48e6f2fe568a8a9ce3193ee5b805ba2e (diff) | |
| download | ast2050-yocto-poky-3e4d84aea3623d4eac2e5a094cf103b26859a6b6.zip ast2050-yocto-poky-3e4d84aea3623d4eac2e5a094cf103b26859a6b6.tar.gz | |
arch-mips.inc: Add the MIPS ABIEXTENSION to toolchain name
[YOCTO #7143]
When the system is configured for a multilib SDK, such as:
require conf/multilib.conf
MULTILIBS = "multilib:lib32 multilib:lib64"
DEFAULTTUNE = "mips32r2"
DEFAULTTUNE_virtclass-multilib-lib32 = "mips64-n32"
DEFAULTTUNE_virtclass-multilib-lib64 = "mips64"
Only one of the mips64-n32 or mips64 toolchains is built. Causing the
other to be unavailable. This is due to both recipes ending up with the
same PN.
The toolchain uses the TRANSLATED_TARGET_ARCH in it's name, however the
target for mips64 and mips64 n32 were the same, causing the conflict.
Avoid this conflict by adding the ABIEXTENSION to the name.
(From OE-Core rev: 0bcc01121e928d0be7a0550e500425852c63cf98)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/conf')
| -rw-r--r-- | meta/conf/machine/include/mips/arch-mips.inc | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/meta/conf/machine/include/mips/arch-mips.inc b/meta/conf/machine/include/mips/arch-mips.inc index 02626d3..08d8fdc 100644 --- a/meta/conf/machine/include/mips/arch-mips.inc +++ b/meta/conf/machine/include/mips/arch-mips.inc @@ -100,3 +100,5 @@ TUNE_FEATURES_tune-mips64el-nf = "n64" BASE_LIB_tune-mips64el-nf = "lib64" MIPSPKGSFX_VARIANT_tune-mips64el-nf = "${TUNE_ARCH}" PACKAGE_EXTRA_ARCHS_tune-mips64el-nf = "mips64el-nf" + +TRANSLATED_TARGET_ARCH_append = "${ABIEXTENSION}" |
