All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	meta-freescale Mailing List <meta-freescale@yoctoproject.org>,
	"Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>
Subject: Re: Heads up on gcc 5.X issues for meta-fsl-arm and meta-fsl-ppc
Date: Fri, 7 Aug 2015 09:40:47 -0400	[thread overview]
Message-ID: <55C4B55F.6070305@gmail.com> (raw)
In-Reply-To: <1438033095.821.291.camel@linuxfoundation.org>

On 07/27/15 17:38, Richard Purdie wrote:
> It appears that gcc 5.x is going to cause a few issues for meta-fsl-arm
> and meta-fsl-ppc. Many of the remaining issues are specific to these
> layers.
> 
> http://errors.yoctoproject.org/Errors/Search/?items=10&query=00957782f4dec7f39b79211e6a2a2bea6f14d2a0&limit=50

I'm looking through all the logs and information on the errors.yp.o site
and I can't seem to figure out what configuration was used for this
build. Specifically, looking through

https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm-lsb/builds/415

I see "CreateAutoConf" tasks, but nowhere in those configurations is the
compiler being set to gcc-5.2%. If I clone meta-fsl-arm and poky, switch
both of them to master-next, and perform a simple build, the
cross-compiler being built is gcc-4.9.3.

Looking through the errors.yp.o website, how do I extract the full
configuration that was used for any given build so that I can duplicate
the build failure?

Best regards,
	Trevor


  parent reply	other threads:[~2015-08-07 13:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 21:38 Heads up on gcc 5.X issues for meta-fsl-arm and meta-fsl-ppc Richard Purdie
2015-07-28  3:10 ` Luo Zhenhua
2015-07-28 17:18   ` Otavio Salvador
2015-07-28 18:30     ` Otavio Salvador
2015-08-06 13:07 ` Trevor Woerner
2015-08-06 13:10   ` Otavio Salvador
2015-08-06 18:08     ` Trevor Woerner
2015-08-07 13:40 ` Trevor Woerner [this message]
2015-08-07 13:54   ` Otavio Salvador
2015-08-07 14:36   ` 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=55C4B55F.6070305@gmail.com \
    --to=twoerner@gmail.com \
    --cc=elizabeth.flanagan@intel.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.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.