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:43 +0000 |
| commit | 0bcc01121e928d0be7a0550e500425852c63cf98 (patch) | |
| tree | 28f9ec076d5135f486fd4eafd973df7fa5435d19 /meta/recipes-bsp/grub/grub2.inc | |
| parent | eaea05c88661a88a89fa6b139f7e6b243155d492 (diff) | |
| download | openembedded-core-0bcc01121e928d0be7a0550e500425852c63cf98.tar.gz openembedded-core-0bcc01121e928d0be7a0550e500425852c63cf98.tar.bz2 openembedded-core-0bcc01121e928d0be7a0550e500425852c63cf98.zip | |
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.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-bsp/grub/grub2.inc')
0 files changed, 0 insertions, 0 deletions