All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: poky <poky@yoctoproject.org>
Subject: Re: Master stability update
Date: Thu, 27 Jan 2011 21:45:26 +0000	[thread overview]
Message-ID: <1296164726.27814.8752.camel@rex> (raw)
In-Reply-To: <95D49026-CF08-4DB9-9749-3C191C737414@dominion.thruhere.net>

On Thu, 2011-01-27 at 16:35 +0100, Koen Kooi wrote:
> Op 27 jan 2011, om 16:06 heeft Richard Purdie het volgende geschreven:
> 
> > On Thu, 2011-01-27 at 13:45 +0100, Koen Kooi wrote:
> >> Op 25 jan 2011, om 23:07 heeft Richard Purdie het volgende geschreven:
> > It seems that autoconf.bbclass change is having a weird ripple effect
> > with the sstate packages. Can you clean sstate and then retry, just to
> > try and isolate the issues?
> > 
> > I agree having a simple change to autotools.bbclass ripple through
> > sstate like that isn't desirable btw, I just want to try and fix one
> > issue at a time.
> 
> I removed tmp, sstate-cache and pseudodone, then did 'bitbake
> console-image', which failed at the same point. I looked into
> '/OE/tentacle/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/bin/', which had a lot files in it, but no autoconf, so I did 'bitbake autoconf-native', that (re)ran a lot of rm_work tasks.
> 
> 
> koen@dominion:/OE/tentacle$ ls /OE/tentacle/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/bin/
> tclConfig.sh*
> 
> so it removed pretty much everything from the sysroot!

Just to update on this, Koen is using distribute_sources which adds a
do_distribute_sources task. This is why things are working on master but
not for Koen.

That task runs later and causes do_setscene to rerun which cleans out
the sysroot rather helpfully assuming that all tasks for that recipe
will rerun which isn't true.

This branch has some proposed changes to make this work better:

http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=rpurdie/misc2

and Koen is testing them to see how they work out.

Cheers,

Richard




  parent reply	other threads:[~2011-01-27 21:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 22:07 Master stability update Richard Purdie
2011-01-26  2:45 ` Xu, Dongxiao
2011-01-26  2:52   ` Tian, Kevin
2011-01-26  3:05     ` Tian, Kevin
2011-01-26  3:51       ` Mark Hatle
2011-01-26 11:42         ` Richard Purdie
2011-01-26  3:52       ` Xu, Dongxiao
2011-01-26  3:55         ` Xu, Dongxiao
2011-01-26 10:01         ` Richard Purdie
2011-01-26 10:31           ` Tian, Kevin
2011-01-26  6:58 ` Saul Wold
2011-01-26  7:01   ` Xu, Dongxiao
2011-01-27 12:45 ` Koen Kooi
2011-01-27 15:06   ` Richard Purdie
2011-01-27 15:35     ` Koen Kooi
2011-01-27 17:01       ` Koen Kooi
2011-01-27 21:45       ` Richard Purdie [this message]
2011-01-27 23:33         ` Koen Kooi
2011-01-28  7:56         ` Koen Kooi
2011-01-28 16:59           ` Richard Purdie
2011-01-28 17:42             ` Koen Kooi

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=1296164726.27814.8752.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=koen@dominion.thruhere.net \
    --cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.