From e7cfbf616f0bc524f9487d98c6e39e30ef28a639 Mon Sep 17 00:00:00 2001 From: Raphael Kubo da Costa Date: Fri, 22 Sep 2017 14:03:43 +0200 Subject: [PATCH] Explicitly set the use_gold GN variable. So far we were assuming ld.gold was always present and preferred. While this tends not to be an issue and upstream only tests gold in its builds (it's faster and uses less memory), we need to respect the ld-is-gold DISTRO_FEATURE. Doing so also helps when building the native bits, as gold's presence in the host system is less likely than in the target toolchain. Signed-off-by: Raphael Kubo da Costa --- recipes-browser/chromium/chromium_61.0.3163.100.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/recipes-browser/chromium/chromium_61.0.3163.100.bb b/recipes-browser/chromium/chromium_61.0.3163.100.bb index 6c5fa75..fe62154 100644 --- a/recipes-browser/chromium/chromium_61.0.3163.100.bb +++ b/recipes-browser/chromium/chromium_61.0.3163.100.bb @@ -208,6 +208,7 @@ GN_ARGS += '\ is_clang=false \ linux_use_bundled_binutils=false \ target_cpu="${@gn_arch_name('${TUNE_ARCH}')}" \ + use_gold=${@bb.utils.contains('DISTRO_FEATURES', 'ld-is-gold', 'true', 'false', d)} \ v8_snapshot_toolchain="//build/toolchain/yocto:yocto_target" \ '