Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Issues with gcc 4.8 sstate "contamination" on the autobuilder
Date: Fri, 31 May 2013 10:12:08 -0500	[thread overview]
Message-ID: <51A8BDC8.4050002@windriver.com> (raw)
In-Reply-To: <51A78ADA.2060308@juszkiewicz.com.pl>

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.)

> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



  reply	other threads:[~2013-05-31 15:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 16:45 Issues with gcc 4.8 sstate "contamination" on the autobuilder Richard Purdie
2013-05-30 17:22 ` Marcin Juszkiewicz
2013-05-31 15:12   ` Mark Hatle [this message]
2013-05-31 15:13     ` Mark Hatle

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=51A8BDC8.4050002@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox