Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: boost breaks on rebuild
Date: Thu, 15 Mar 2012 20:52:44 +0000	[thread overview]
Message-ID: <1331844764.18586.135.camel@ted> (raw)
In-Reply-To: <CAGDS+nmdJNhd4X2=vSFNsexnXZvE_pOy2vjD-k+6DoLGefFpCA@mail.gmail.com>

On Thu, 2012-03-15 at 12:14 -0700, Steve Sakoman wrote:
> On Thu, Mar 15, 2012 at 9:21 AM, Mark Hatle <mark.hatle@windriver.com> wrote:
> > On 3/15/12 8:39 AM, Richard Purdie wrote:
> >>
> >> On Wed, 2012-03-14 at 15:28 -0700, Steve Sakoman wrote:
> >>>
> >>> NOTE: package boost-1.49.0-r2.0: task do_compile: Failed
> >>>
> >>> I don't have a fix for this but wanted to document the failure.
> >>>
> >>> As with all the other failures of this type, a -c cleansstate and
> >>> rebuild is the workaround.
> >>>
> >>> It feels to me like there are quite a few recipes that don't handle
> >>> rebuilds -- I seem to run into a few after every pull.
> >
> >
> > I've observed the same thing.  There seem to be a lot of packages that once
> > they've been configured, compiled and installed, won't rebuild without being
> > cleaned in someway.
> 
> This is the one that really pisses me off, happens after every pull on
> my Ubuntu 64 bit build machine:
> 
> Summary: 1 task failed:
>   virtual:native:/home/steve/source/yocto/poky/meta/recipes-devtools/pseudo/pseudo_1.2.bb,
> do_compile
> Summary: There were 8 WARNING messages shown.
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> 
> No simple fix since any bitbake command complains about needing to
> rebuild psuedo:
> 
> Pseudo is not present but is required, building this first before the main build
> 
> And of course the psuedo rebuild instantly fails!

Sounds like we need to teach the wrapper script to allow a pseudo-native
to be passed -c options directly (and fix pseudo's makefile if needed).

Cheers,

Richard




      reply	other threads:[~2012-03-15 21:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 22:28 boost breaks on rebuild Steve Sakoman
2012-03-15 13:39 ` Richard Purdie
2012-03-15 16:21   ` Mark Hatle
2012-03-15 19:14     ` Steve Sakoman
2012-03-15 20:52       ` Richard Purdie [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=1331844764.18586.135.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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