From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/4] perf: fix for rebuilding
Date: Wed, 21 Jan 2015 07:23:17 +0800 [thread overview]
Message-ID: <54BEE365.7050809@windriver.com> (raw)
In-Reply-To: <CAJTo0LazYTzaTiszo9++cgNmJca9S0G0jO7-omsqKqrS_4x4+g@mail.gmail.com>
On 01/21/2015 01:00 AM, Burton, Ross wrote:
>
> On 20 January 2015 at 16:01, Bruce Ashfield <bruce.ashfield@gmail.com
> <mailto:bruce.ashfield@gmail.com>> wrote:
>
> The kernel source is no longer in this location .. so at a minimum the header
> needs to be updated to log the work-shared directory .. and better, make sure
> that this is still happening with the latest master changes.
>
>
> As I understand it the bug is stale .d files being used to add dependencies,
> which refer to stale paths instead of being re-generated. This is why we
> encourage S!=B with deletion of B when starting builds.
Yes, you are right, sounds good, I will update the patch about 2 hours later.
// Robert
>
> Ross
next prev parent reply other threads:[~2015-01-20 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 7:11 [PATCH 0/4] meta: 4 fixes Robert Yang
2015-01-19 7:11 ` [PATCH 1/4] cpan-base.bbclass: avoid using immmediate assignment for PERLLIBDIRS Robert Yang
2015-01-19 7:11 ` [PATCH 2/4] python3: fix for cross compiling Robert Yang
2015-01-19 7:11 ` [PATCH 3/4] gnutls: fix sed command Robert Yang
2015-01-19 7:11 ` [PATCH 4/4] perf: fix for rebuilding Robert Yang
2015-01-20 15:58 ` Burton, Ross
2015-01-20 16:01 ` Bruce Ashfield
2015-01-20 17:00 ` Burton, Ross
2015-01-20 23:23 ` Robert Yang [this message]
2015-01-20 23:45 ` Robert Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54BEE365.7050809@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox