linux-yocto and gcc 5.x
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:
(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
Quoted 7 lines · Richard Purdie
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:
Quoted 6 lines
(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.
What's the incantation to configure gcc5 into a test build ?
Bruce
Quoted 7 lines
Cheers,
Richard
Quoted 10 lines · Bruce Ashfield
Quoted 9 lines · Richard Purdie
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:
Quoted 8 lines
Quoted 4 lines
(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.
Quoted 1 line
What's the incantation to configure gcc5 into a test build ?
or just set
GCCVERSION = "5.1%"
Cheers,
Richard
Quoted 8 lines · Richard Purdie
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:
as mentioned in another thread. linux-yocto needs to backport
https://patchwork.ozlabs.org/patch/403787/
to beging with. I have 3.8 running on beaglebone white but thats not linux-yocto
https://github.com/koenkooi/meta-beagleboard/commit/07e27c22e707e26f3f321f51999c4f6a294b5b18
https://github.com/koenkooi/meta-beagleboard/commit/765e7f35af7e4358573868389d4ea144eacd6b7a
there is a patch or two in there that needs to go upstream into kernel as well but I havent bothered yet.
I was not able to boot linux yocto 3.19 few weeks ago on any of emulators when build with gcc5
rootfs did not have any issues.
I also have 3.10 compiling and booting on another Arm platform
Quoted 6 lines
(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,
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
Quoted 20 lines · Richard Purdie
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:
(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
I'll do an explicit round of gcc5 support in master for the kernels we have there in the not to distant future. To throw the switch for gcc5, we'll obviously want all the architectures to build and boot.
To keep things practical, I'll start from the -dev kernel, then back to the LTSI kernels we still have in master.
In the meantime, if anyone has patches, sending them to the linux-yocto mailing list is appreciated. Since everyone has eyes and ears on different lists it makes the effort that much easier if we collect changes in advance on a single list.
Bruce
Quoted 44 lines · Robert Yang
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.omake[2]: *** [
arch/arm64/kernel] Error 2
make[2]: *** Waiting for unfinished jobs....// Robert
Quoted 21 lines · Richard Purdie
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:
(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
Robert,
this was the error I hit last week. There may be a fix I have not tried.
https://lkml.org/lkml/2015/2/18/422
- armin
Quoted 44 lines · Robert Yang
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.omake[2]: *** [
arch/arm64/kernel] Error 2
make[2]: *** Waiting for unfinished jobs....// Robert
Quoted 21 lines · Richard Purdie
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:
(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