[OE-core] linux-yocto and gcc 5.x
Robert Yang
liezhi.yang at windriver.com
Wed May 13 07:39:25 UTC 2015
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
>
>
>
More information about the Openembedded-core
mailing list