diff options
| author |   Christopher Larson <kergoth@gmail.com> | 2015-07-01 08:18:21 -0700 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-07-07 23:57:12 +0100 |
| commit | 4d208ebacb3a5d189998ac9be6d1a454c45aa975 (patch) | |
| tree | a483540506eb4a2fec67518ca6ec162d8a99d3d4 /meta | |
| parent | 8df57b4b1a110dcbaab9652795fe5c0d86019554 (diff) | |
| download | openembedded-core-contrib-4d208ebacb3a5d189998ac9be6d1a454c45aa975.tar.gz | |
multilib_global: expand multilib pref values properly
This ensures that in cases where the preference value changes when the
multilib override is applied, we correctly expand it in that context.
For example, for `PREFERRED_PROVIDER_${TARGET_PREFIX}gcc
= "gcc-external-cross-${TARGET_ARCH}"`, when it sets the prefixed version of
this, we want TARGET_ARCH expanded with the multilib applied, otherwise the
arch suffix will be incorrect for that context.
We ran into this trying to use preferences in meta-sourcery along with
multilibs. We worked around it there via PNBLACKLIST, but this fix should
still go into the core.
Signed-off-by: Christopher Larson <kergoth@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta')
| -rw-r--r-- | meta/classes/multilib_global.bbclass | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/classes/multilib_global.bbclass b/meta/classes/multilib_global.bbclass index 67bd70d293..ed34404117 100644 --- a/meta/classes/multilib_global.bbclass +++ b/meta/classes/multilib_global.bbclass @@ -84,7 +84,7 @@ def preferred_ml_updates(d): # implement alternative multilib name newname = localdata.expand("PREFERRED_PROVIDER_" + virt + p + "-" + pkg) if not d.getVar(newname, False): - d.setVar(newname, newval) + d.setVar(newname, localdata.expand(newval)) # Avoid future variable key expansion provexp = d.expand(prov) if prov != provexp and d.getVar(prov, False): |