aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-connectivity/nfs-utils/nfs-utils_1.3.1.bb
diff options
context:
space:
mode:
authorRobert Yang <liezhi.yang@windriver.com>2015-07-03 01:03:18 -0700
committerRobert Yang <liezhi.yang@windriver.com>2015-07-03 01:39:44 -0700
commit1f153bbbdc6b7db05529fda3b36464f646f8fcb8 (patch)
tree20b3f3a3e18492f76b017c03667d8056dd28c360 /meta/recipes-connectivity/nfs-utils/nfs-utils_1.3.1.bb
parentdd09fab685de2eaf04aa5ab60f8220b89c1deae9 (diff)
downloadopenembedded-core-contrib-rbt/cross.tar.gz
openembedded-core-contrib-rbt/cross.tar.bz2
openembedded-core-contrib-rbt/cross.zip
multilib_global.bbclass: fix PREFERRED_VERSION for cross-canadianrbt/cross
Fixed: When both gcc 4.9 and 5.1 are in the layer, and set these in local.conf: GCCVERSION = "4.9%" MACHINE = "qemux86-64" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" $ bitbake gcc-cross-canadian-i586 Then gcc 5.1 would be built rather than 4.9, it is because multilib_virtclass_handler() doesn't reset PN such as gcc-cross-canadian to lib32-gcc-cross-canadian, but preferred_ml_updates() rename PREFERRED_VERSION_gcc-cross-canadian to PREFERRED_VERSION_lib32-gcc-cross-canadian, so it can't get the required value PREFERRED_VERSION_gcc-cross-canadian, and then gcc 5.1 would be used, don't reset it in preferred_ml_updates() will fix the problem. [YOCTO #7950] Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Diffstat (limited to 'meta/recipes-connectivity/nfs-utils/nfs-utils_1.3.1.bb')
0 files changed, 0 insertions, 0 deletions