[OE-core] boost breaks on rebuild

[Steve Sakoman]

On Thu, Mar 15, 2012 at 9:21 AM, Mark Hatle <mark.hatle at 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!

Steve

> 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 at lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core