From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by mail.openembedded.org (Postfix) with ESMTP id BDB2F6F9D1 for ; Tue, 25 Mar 2014 03:18:48 +0000 (UTC) Received: from ALA-HCB.corp.ad.wrs.com (ala-hcb.corp.ad.wrs.com [147.11.189.41]) by mail1.windriver.com (8.14.5/8.14.5) with ESMTP id s2P3IjD6011936 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 24 Mar 2014 20:18:45 -0700 (PDT) Received: from [128.224.162.226] (128.224.162.226) by ALA-HCB.corp.ad.wrs.com (147.11.189.41) with Microsoft SMTP Server id 14.3.169.1; Mon, 24 Mar 2014 20:18:41 -0700 Message-ID: <5330F58F.3040501@windriver.com> Date: Tue, 25 Mar 2014 11:18:39 +0800 From: Robert Yang User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Chris Larson , "Purdie, Richard" References: <12217d8620e434a88433e7a60ff7fa8a1b51c6b1.1395713906.git.liezhi.yang@windriver.com> In-Reply-To: Cc: Patches and discussions about the oe-core layer Subject: Re: [PATCH 1/1] meta/conf/bitbake.conf: add STAMPCLEAN to BB_HASHBASE_WHITELIST X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Mar 2014 03:18:52 -0000 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit On 03/25/2014 10:20 AM, Chris Larson wrote: > On Mon, Mar 24, 2014 at 7:18 PM, Robert Yang wrote: > >> The problem is that do_configure.sigdata depends on STAMPS_DIR because: >> >> do_configure -> STAMPCLEAN -> STAMPS_DIR >> >> this will make the sigdata generated by "STAMPS_DIR=/tmp/stps bitbake -S >> recipe" doesn't match the ones in our build dir, but it should. We can >> add STAMPS_DIR or STAMPCLEAN to BB_HASHBASE_WHITELIST to fix the >> problem, but we can't add STAMPS_DIR since once it is in >> BB_HASHBASE_WHITELIST, the "STAMPS_DIR=/tmp/stps bitbake -S recipe" >> would not run again. >> >> [YOCTO $6031] >> >> Signed-off-by: Robert Yang >> > > Oh good, I was hoping someone would dig into this, hadn't had the time, but > kept noticing STAMPS_DIR was leaking in, in the bitbake-whatchanged output > :) Nice work. > Thanks, the bitbake-whatchanged will work with another base-files fix now. The left problem is that: $ bitbake-whatchanged core-image-sato-sdk === Newly added tasks: (3 tasks) core-image-sato-sdk: do_compile do_configure do_install Nothing should be run in fact, the root cause is that "bitbake -S recipe" generates the sigdata file for all the tasks including noexec one, but "bitbake recipe" doesn't generate stamps for do_populate_sysroot's dependencies tasks when: do_populate_sysroot[noexec] = "1" We also have these set for a image recipe: [snip] do_install[noexec] = "1" do_compile[noexec] = "1" do_configure[noexec] = "1" [snip] If we remove 'do_populate_sysroot[noexec] = "1"' and keep the others, then "bitbake recipe" will generate stamps for all the tasks including do_install, do_compile and do_configure though they have noexec set. I've tried to dig lib/bb/build.py, lib/bb/siggen.py and lib/bb/runqueue.py, but didn't figure it out. For bitbake-whatchanged, maybe we can enhance the "bitbake -S" in YP 1.7 to do the similar thing since the later one can handle the sstate tasks (and covered task) better. // Robert