Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] autotools.bbclass: Add functionality to force a distclean when reconfiguring
Date: Sat, 8 Sep 2012 10:49:27 -0500	[thread overview]
Message-ID: <504B6907.6080704@windriver.com> (raw)
In-Reply-To: <1347119094.2583.20.camel@lenny>

On 9/8/12 10:44 AM, Colin Walters wrote:
> On Fri, 2012-09-07 at 17:05 +0100, Richard Purdie wrote:
>> Unfortunately whilst reruning 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 a "make distclean" call to recipes where configure is
>> rerunning and the sstate checksum for do_configure has changed. We could
>> simply use a stamp but saving out the previous configuration checksum
>> adds some data at no real overhead.
>
> The major problem with distclean is that it completely falls over in the
> scenario where the source code has changed; the new distclean won't know
> about *old* object files it no longer builds, files renamed, etc.
>
> In GNOME we just this cycle landed this patch to use "git clean -dfx"
> instead of "make distclean" if possible:
> https://bugzilla.gnome.org/show_bug.cgi?id=656081
>
> It might be interesting to have an option to run:
> "git init; git add .; git commit -a -m auto-import" on each tarball
> build in OE.  I've been considering doing this for jhbuild.
>
> (My latest build system *only* builds from git repositories, so
>   it works there =) )

While we're not managing the patching w/ git.. we are with quilt.  Does quilt 
have any facilities for restoring to the pristine last copy vs whatever is in 
the current tree?  (I don't think it does BTW.)

--Mark

>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>




      reply	other threads:[~2012-09-08 16:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 16:05 [PATCH] autotools.bbclass: Add functionality to force a distclean when reconfiguring Richard Purdie
2012-09-07 16:32 ` Mark Hatle
2012-09-07 16:37   ` Richard Purdie
2012-09-07 16:42   ` Burton, Ross
2012-09-07 17:09     ` Richard Purdie
2012-09-07 17:15       ` Phil Blundell
2012-09-08  8:05         ` Khem Raj
2012-09-08 13:30           ` Mark Hatle
2012-09-08 15:36             ` Colin Walters
2012-09-08 15:44 ` Colin Walters
2012-09-08 15:49   ` Mark Hatle [this message]

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=504B6907.6080704@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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