From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Trevor Woerner <twoerner@gmail.com>
Cc: 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, 07 Aug 2015 09:36:25 -0500 [thread overview]
Message-ID: <1438958185.30467.50.camel@linuxfoundation.org> (raw)
In-Reply-To: <55C4B55F.6070305@gmail.com>
On Fri, 2015-08-07 at 09:40 -0400, Trevor Woerner wrote:
> 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?
If you lookup the git revision of master-next that was built, you'd find
there was a patch included which tweaked the gcc version. The patch
included was:
http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/t222&id=e3a291d8dd3afd142e0723526055c1c1cc44d8c3
Cheers,
Richard
prev parent reply other threads:[~2015-08-07 14:36 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
2015-08-07 13:54 ` Otavio Salvador
2015-08-07 14:36 ` Richard Purdie [this message]
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=1438958185.30467.50.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=elizabeth.flanagan@intel.com \
--cc=meta-freescale@yoctoproject.org \
--cc=twoerner@gmail.com \
/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.