Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-core@lists.openembedded.org
Subject: Re: Issues with gcc 4.8 sstate "contamination" on the autobuilder
Date: Thu, 30 May 2013 19:22:34 +0200	[thread overview]
Message-ID: <51A78ADA.2060308@juszkiewicz.com.pl> (raw)
In-Reply-To: <1369932321.14887.320.camel@ted>

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.


  reply	other threads:[~2013-05-30 17:23 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 [this message]
2013-05-31 15:12   ` Mark Hatle
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=51A78ADA.2060308@juszkiewicz.com.pl \
    --to=marcin@juszkiewicz.com.pl \
    --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