From: Robert Yang <liezhi.yang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"Ashfield, Bruce" <Bruce.Ashfield@windriver.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: linux-yocto and gcc 5.x
Date: Wed, 13 May 2015 15:39:25 +0800 [thread overview]
Message-ID: <5552FFAD.4070306@windriver.com> (raw)
In-Reply-To: <1431350446.30971.56.camel@linuxfoundation.org>
I think that I met another problem when MACHINE = qemuarm64 with gcc5:
linux-yocto_3.19.bb:
/tmp/ccWk2lM2.s: Assembler messages:
/tmp/ccWk2lM2.s:42: Error: .err encountered
/tmp/ccWk2lM2.s:43: Error: .err encountered
/tmp/ccWk2lM2.s:44: Error: .err encountered
/tmp/ccWk2lM2.s:103: Error: .err encountered
/tmp/ccWk2lM2.s:104: Error: .err encountered
/tmp/ccWk2lM2.s:105: Error: .err encountered
make[3]: *** [arch/arm64/kernel/psci.o] Error 1
make[3]: *** Waiting for unfinished jobs....
CC mm/mmzone.o
CC mm/vmstat.o
CC mm/backing-dev.o
CC net/socket.o
make[2]: *** [arch/arm64/kernel] Error 2
make[2]: *** Waiting for unfinished jobs....
// Robert
On 05/11/2015 09:20 PM, 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?
>
> Cheers,
>
> Richard
>
>
>
next prev parent reply other threads:[~2015-05-13 7:39 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
2015-05-11 15:53 ` Khem Raj
2015-05-13 7:39 ` Robert Yang [this message]
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=5552FFAD.4070306@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=Bruce.Ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.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.