From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: linux-yocto and gcc 5.x
Date: Mon, 11 May 2015 14:57:05 +0100 [thread overview]
Message-ID: <1431352625.30971.60.camel@linuxfoundation.org> (raw)
In-Reply-To: <5550B3DB.3030109@windriver.com>
On Mon, 2015-05-11 at 09:51 -0400, Bruce Ashfield wrote:
> On 2015-05-11 09:20 AM, Richard Purdie wrote:
> > Hi Bruce,
> >
> > One of the things we're looking at in 1.9 is gcc 5.x support by default.
> > One of the areas this has significant impact is on the kernels,
> > linux-yocto in particular. I'm starting to see a potential problem here
> > since the kernels don't appear to work well with gcc 5.x:
> >
> > http://errors.yoctoproject.org/Errors/Search/?items=10&query=1426e31f0bcd19f066931d2ecbdec3752b14e88e&limit=150&order_by=RECIPE
> >
> > (this is a test build I ran just to see how bad things were).
> >
> > Are we going to be in a position to get 5.x support backported into 3.14
> > (and maybe 3.10)? Or was we going to have to wait for later versions?
>
> I should be able to bring gcc5 support back to the previous LTSI
> kernel (3.14), but need to poke at the breakage myself to know
> for sure.
Sorry, I was confused with versions, I of course mean 3.17 and 3.14
above, we dropped 3.10! I think 3.17 is ok so its 3.14 that we're having
the problems with by the looks of it.
> What's the incantation to configure gcc5 into a test build ?
http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=d72ca3dca225a4801e595c95e98aacbe738d8303
or just set
GCCVERSION = "5.1%"
Cheers,
Richard
next prev parent reply other threads:[~2015-05-11 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 13:20 linux-yocto and gcc 5.x Richard Purdie
2015-05-11 13:51 ` Bruce Ashfield
2015-05-11 13:57 ` Richard Purdie [this message]
2015-05-11 15:53 ` Khem Raj
2015-05-13 7:39 ` Robert Yang
2015-05-13 14:25 ` Bruce Ashfield
2015-05-13 17:44 ` akuster808
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=1431352625.30971.60.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@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