[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openembedded-core
Subject:    [OE-core] Issues with gcc 4.8 sstate "contamination" on the autobuilder
From:       mark.hatle () windriver ! com (Mark Hatle)
Date:       2013-05-31 15:13:59
Message-ID: 51A8BE37.5000008 () windriver ! com
[Download RAW message or body]

On 5/31/13 10:12 AM, Mark Hatle wrote:
> On 5/30/13 12:22 PM, Marcin Juszkiewicz wrote:
>> W dniu 30.05.2013 18:45, Richard Purdie pisze:
>>> I want to make people aware we're seeing some issues with gcc 4.8 on the
>>> autobuilder.
>>
>> When we are at sstate and gcc...
>>
>> I noticed recently that libunwind may break gcc builds:
>>
>> https://bugs.launchpad.net/linaro-oe/+bug/1183087
>>
>> The issue exists only when libunwind was built before gcc was started.
>>
>> To reproduce:
>>
>> bitbake -ccleansstate gcc libunwind
>> bitbake libunwind
>> bitbake gcc
>>
>> Did not yet found proper working solution.
>
> Just an FYI -- I've reproduced the same issue here for an qemux86_64 machine
> using stock oe-core.
>
> (Similarly, I don't have a solution either.)

Forgot to add in my case the sstate cache had nothing to do with it.  If 
libunwind is built first, then gcc appears to fail.  Cleaning both and 
rebuilding gcc caused it to work.

--Mark

[prev in list] [next in list] [prev in thread] [next in thread]