From 1f2a3cdadac1560b0e03a7be25f452ad48c27ddb Mon Sep 17 00:00:00 2001 From: Patrick Ohly Date: Fri, 13 Jan 2017 15:52:31 +0100 Subject: gcc-source.inc: cleanly disable do_rm_work Using "deltask" assumes that do_rm_work has been added already, which won't be the case anymore in the upcoming improved rm_work.bbclass, because then an anonymous python method will add do_rm_work. Setting RM_WORK_EXCLUDE works with the current and upcoming rm_work.bbclass and is the API that is meant to be used for excluding recipes from cleaning, so use that. Signed-off-by: Patrick Ohly Signed-off-by: Ross Burton --- meta/recipes-devtools/gcc/gcc-source.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/gcc/gcc-source.inc b/meta/recipes-devtools/gcc/gcc-source.inc index 49bde92c49..0d0edb58f0 100644 --- a/meta/recipes-devtools/gcc/gcc-source.inc +++ b/meta/recipes-devtools/gcc/gcc-source.inc @@ -3,7 +3,7 @@ deltask do_compile deltask do_install deltask do_populate_sysroot deltask do_populate_lic -deltask do_rm_work +RM_WORK_EXCLUDE += "${PN}" inherit nopackages -- cgit 1.2.3-korg