From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "Garman, Scott A" <scott.a.garman@intel.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] autotools.bbclass: Add functionality to force a clean of ${B} when reconfiguring (and ${S} != ${B})
Date: Wed, 12 Sep 2012 15:16:26 +0100 [thread overview]
Message-ID: <1347459386.11710.23.camel@ted> (raw)
In-Reply-To: <70CC66F5C30A414DADDA6973E4CA391A66FF3F@039-SN1MPN1-001.039d.mgd.msft.net>
On Tue, 2012-09-11 at 19:01 +0000, McClintock Matthew-B29882 wrote:
> On Tue, Sep 11, 2012 at 9:22 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > Unfortunately whilst rerunning configure and make against a project will mostly
> > work there are situations where it does not correctly do the right thing.
> >
> > In particular, eglibc and gcc will fail out with errors where settings
> > do not match a previously built configuration. It could be argued they are
> > broken but the situation is what it is. There is the possibility of more subtle
> > errors too.
> >
> > This patch adds removal of the build directory (${B}) when configure is
> > rerunning, the sstate checksum for do_configure has changed and ${S} != ${B}.
> > We could simply use a stamp but saving out the previous configuration checksum
> > adds some data at no real overhead.
> >
> > If we find there are things where we want to disable this behaviour with
> > CONFIGURESTAMPFILE = "" in the recipe, or users could disable it globally.
> >
> > [YOCTO #2774]
> > [YOCTO #2848]
> >
> > This is particularly helpful for eglibc and gcc which use split builds by default and
> > are a particular source of reconfigure type problems.
> >
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> Is it feasible to back port this to denzil? I've encountered what I
> think are similar issues reconfiguring gcc for example.
One of the bugs above is open against denzil and the issue certainly
exists there. The patch should apply equally well there.
I'd suggest we let this settle in master for a week or two and then add
it to the backport queue if no problems arise.
Cc'ing Scott so he's aware of this.
Cheers,
Richard
next prev parent reply other threads:[~2012-09-12 14:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 14:22 [PATCH] autotools.bbclass: Add functionality to force a clean of ${B} when reconfiguring (and ${S} != ${B}) Richard Purdie
2012-09-11 19:01 ` McClintock Matthew-B29882
2012-09-12 14:16 ` Richard Purdie [this message]
2012-09-12 17:47 ` McClintock Matthew-B29882
2012-09-14 0:26 ` Scott Garman
2012-09-26 17:07 ` Phil Blundell
2012-09-26 23:45 ` McClintock Matthew-B29882
2012-09-28 13:23 ` Richard Purdie
2012-09-28 20:21 ` McClintock Matthew-B29882
2012-09-28 21:20 ` Richard Purdie
2012-09-29 6:42 ` Ross Burton
2012-09-29 7:24 ` Martin Jansa
2012-09-29 10:30 ` Richard Purdie
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=1347459386.11710.23.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=B29882@freescale.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=scott.a.garman@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