From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: boost breaks on rebuild
Date: Thu, 15 Mar 2012 11:21:47 -0500 [thread overview]
Message-ID: <4F62171B.4060203@windriver.com> (raw)
In-Reply-To: <1331818796.18586.85.camel@ted>
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.
One suggestion, maybe a new flag for a recipe that says that recipe rebuilds
need to start from a clean patched tree? Then if the do_configure -> do_install
steps have been run, it knows it needs to clean and fetch/unpack/patch before it
tries to rebuild the component... (Maybe sstate-cache can help speed this up in
some way...)
Then over time we can find the items with the flags and attempt to fix them in
other ways...
--Mark
> Agreed, there is a problem here. I've filed the bug:
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=2123
>
> since I think we systematically need to work through these and eradicate
> them.
>
> An alternative to fix some of the compile cases would be to run a "make
> clean" before the make. I suspect this would annoy people and its a
> shame to do that because of a few broken recipes though...
>
> Cheers,
>
> Richard
>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2012-03-15 16:30 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 [this message]
2012-03-15 19:14 ` Steve Sakoman
2012-03-15 20:52 ` 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=4F62171B.4060203@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 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.