Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: oe-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] autotools: Attempt to clean build directory when rerunning configure
Date: Tue, 30 Oct 2012 12:19:39 +0000	[thread overview]
Message-ID: <1351599582.13864.52.camel@phil-desktop> (raw)
In-Reply-To: <1351584642.2828.58.camel@ted>

On Tue, 2012-10-30 at 08:10 +0000, Richard Purdie wrote:
> How extensively has this been tested? I have a suspicion that we might
> run into a number of issues doing this throughout the tree :(

I've had this in my tree for a few weeks and the only package I've found
so far that went wrong was polkit, see separate patch for that.  (There
a few other packages for which "make clean" fails in a harmless manner.)
But it's true that I haven't built the whole of world this way yet.

>I'm wondering how many recipes will suffer from issues with "make
>clean" verses how many recipes would struggle if we defaulted 
>${B} != ${S}?

My guess is that "make clean" is slightly more likely to work (or, at
least, not break anything) on average.  But defaulting ${B} != ${S}
would definitely be a desirable thing in the longer term and I would
certainly be in favour of moving in that direction.

p.





      reply	other threads:[~2012-10-30 12:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 18:14 [PATCH] autotools: Attempt to clean build directory when rerunning configure Phil Blundell
2012-10-30  8:10 ` Richard Purdie
2012-10-30 12:19   ` Phil Blundell [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=1351599582.13864.52.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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