rpm: fix build issue with gcc5
PATCH 1/1 rpm: fix build issue with gcc5
| tset.o:(.debug_loc+0xe8): undefined reference to .LCL0' | tset.o:(.debug_loc+0xf7): undefined reference to .LCL0'
thanks Khem
--- meta/recipes-devtools/rpm/rpm_5.4.14.bb | 3 +++ 1 file changed, 3 insertions(+)
meta/recipes-devtools/rpm/rpm_5.4.14.bb +3 -0
@@ -110,6 +110,9 @@ inherit autotools gettext acpaths = "-I ${S}/db/dist/aclocal -I ${S}/db/dist/aclocal_java" +FULL_OPTIMIZATION_powerpc_remove = "-O2" +FULL_OPTIMIZATION_append_powerpc = " -Os " + # Specify the default rpm macros in terms of adjustable variables rpm_macros = "%{_usrlibrpm}/macros:%{_usrlibrpm}/poky/macros:%{_usrlibrpm}/poky/%{_target}/macros:%{_etcrpm}/macros.*:%{_etcrpm}/macros:%{_etcrpm}/%{_target}/macros:~/.oerpmmacros" rpm_macros_class-native = "%{_usrlibrpm}/macros:%{_usrlibrpm}/poky/macros:%{_usrlibrpm}/poky/%{_target}/macros:~/.oerpmmacros"
Signature · 1 line
2.3.5
Quoted 15 lines · Armin Kuster
| tset.o:(.debug_loc+0xe8): undefined reference to
.LCL0' | tset.o:(.debug_loc+0xf7): undefined reference to.LCL0'thanks Khem
Signed-off-by Armin Kuster <[email protected]>--- meta/recipes-devtools/rpm/rpm_5.4.14.bb | 3 +++ 1 file changed, 3 insertions(+)meta/recipes-devtools/rpm/rpm_5.4.14.bb +0
-0
meta/recipes-devtools/rpm/rpm_5.4.14.bb inherit autotools gettext · line 115
Quoted 6 lines
meta/recipes-devtools/rpm/rpm_5.4.14.bb +3
-0@@ -110,6 +110,9 @@ inherit autotools gettext acpaths = "-I ${S}/db/dist/aclocal -I ${S}/db/dist/aclocal_java" +FULL_OPTIMIZATION_powerpc_remove = "-O2" +FULL_OPTIMIZATION_append_powerpc = " -Os " +
http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/master&id=741d3bf91144973d26de647039fa60b87a09edf1
fixes same issue for libx11
I am wondering if we should make this change in some common config metadata file to list all recipes that need this workaround untill gcc is fixed for it may be arch-powerpc.inc, since then it will be easy to remember to unbolt them once gcc is fixed.
Quoted 11 lines
meta/recipes-devtools/rpm/rpm_5.4.14.bb +0
-1# Specify the default rpm macros in terms of adjustable variables rpm_macros = "%{_usrlibrpm}/macros:%{_usrlibrpm}/poky/macros:%{_usrlibrpm}/poky/%{_target}/macros:%{_etcrpm}/macros.*:%{_etcrpm}/macros:%{_etcrpm}/%{_target}/macros:~/.oerpmmacros" rpm_macros_class-native = "%{_usrlibrpm}/macros:%{_usrlibrpm}/poky/macros:%{_usrlibrpm}/poky/%{_target}/macros:~/.oerpmmacros" --2.3.5
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 26 lines · Khem Raj
Quoted 15 lines · Armin Kuster
| tset.o:(.debug_loc+0xe8): undefined reference to
.LCL0' | tset.o:(.debug_loc+0xf7): undefined reference to.LCL0'thanks Khem
Signed-off-by Armin Kuster <[email protected]>--- meta/recipes-devtools/rpm/rpm_5.4.14.bb | 3 +++ 1 file changed, 3 insertions(+)meta/recipes-devtools/rpm/rpm_5.4.14.bb +0
-0meta/recipes-devtools/rpm/rpm_5.4.14.bb inherit autotools gettext · line 115
Quoted 6 lines
meta/recipes-devtools/rpm/rpm_5.4.14.bb +3
-0@@ -110,6 +110,9 @@ inherit autotools gettext acpaths = "-I ${S}/db/dist/aclocal -I ${S}/db/dist/aclocal_java" +FULL_OPTIMIZATION_powerpc_remove = "-O2" +FULL_OPTIMIZATION_append_powerpc = " -Os " +http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/master&id=741d3bf91144973d26de647039fa60b87a09edf1
fixes same issue for libx11
Quoted 4 lines
I am wondering if we should make this change in some common config metadata file to list all recipes that need this workaround untill gcc is fixed for it may be arch-powerpc.inc, since then it will be easy to remember to unbolt them once gcc is fixed.
I like the idea of a common include to handle this a lot better.
FWIW, I tried gcc 5 on the autobuilder. The results were 141 failures so far:
Cheers,
Richard
Quoted 27 lines · Richard Purdie
Quoted 26 lines · Khem Raj
Quoted 15 lines · Armin Kuster
| tset.o:(.debug_loc+0xe8): undefined reference to
.LCL0' | tset.o:(.debug_loc+0xf7): undefined reference to.LCL0'thanks Khem
Signed-off-by Armin Kuster <[email protected]>--- meta/recipes-devtools/rpm/rpm_5.4.14.bb | 3 +++ 1 file changed, 3 insertions(+)meta/recipes-devtools/rpm/rpm_5.4.14.bb +0
-0meta/recipes-devtools/rpm/rpm_5.4.14.bb inherit autotools gettext · line 115
Quoted 6 lines
meta/recipes-devtools/rpm/rpm_5.4.14.bb +3
-0@@ -110,6 +110,9 @@ inherit autotools gettext acpaths = "-I ${S}/db/dist/aclocal -I ${S}/db/dist/aclocal_java" +FULL_OPTIMIZATION_powerpc_remove = "-O2" +FULL_OPTIMIZATION_append_powerpc = " -Os " +http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/master&id=741d3bf91144973d26de647039fa60b87a09edf1
fixes same issue for libx11
Quoted 6 lines
Quoted 4 lines
I am wondering if we should make this change in some common config metadata file to list all recipes that need this workaround untill gcc is fixed for it may be arch-powerpc.inc, since then it will be easy to remember to unbolt them once gcc is fixed.
I like the idea of a common include to handle this a lot better.
Second that.
I will send a patch
- armin
Quoted 10 lines
FWIW, I tried gcc 5 on the autobuilder. The results were 141 failures so far:
Cheers,
Richard
Quoted 7 lines · Richard Purdie
I like the idea of a common include to handle this a lot better.
FWIW, I tried gcc 5 on the autobuilder. The results were 141 failures so far:
linux-yocto 3.14 needs to backport
https://patchwork.ozlabs.org/patch/403787/ for all relvant branches
For some ppc recipes failing with undefined .LCx smbols we need to not use -O2 mips64 is new havent tried and tested those yet
Quoted 3 lines
Cheers,
Richard
Quoted 7 lines · Khem Raj
Quoted 5 lines · Richard Purdie
I like the idea of a common include to handle this a lot better.
FWIW, I tried gcc 5 on the autobuilder. The results were 141 failures so far:
Quoted 8 lines
Quoted 2 lines
linux-yocto 3.14 needs to backport
https://patchwork.ozlabs.org/patch/403787/ for all relvant branchesFor some ppc recipes failing with undefined .LCx smbols we need to not use -O2 mips64 is new havent tried and tested those yet
arm64 kernel build failed don't recall how many packages.
- armin
Quoted 4 lines
Quoted 4 lines
Cheers,
Richard
Quoted 32 lines · Richard Purdie
Quoted 26 lines · Khem Raj
Quoted 15 lines · Armin Kuster
| tset.o:(.debug_loc+0xe8): undefined reference to
.LCL0' | tset.o:(.debug_loc+0xf7): undefined reference to.LCL0'thanks Khem
Signed-off-by Armin Kuster <[email protected]>--- meta/recipes-devtools/rpm/rpm_5.4.14.bb | 3 +++ 1 file changed, 3 insertions(+)meta/recipes-devtools/rpm/rpm_5.4.14.bb +0
-0meta/recipes-devtools/rpm/rpm_5.4.14.bb inherit autotools gettext · line 115
Quoted 6 lines
meta/recipes-devtools/rpm/rpm_5.4.14.bb +3
-0@@ -110,6 +110,9 @@ inherit autotools gettext acpaths = "-I ${S}/db/dist/aclocal -I ${S}/db/dist/aclocal_java" +FULL_OPTIMIZATION_powerpc_remove = "-O2" +FULL_OPTIMIZATION_append_powerpc = " -Os " +http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/master&id=741d3bf91144973d26de647039fa60b87a09edf1
fixes same issue for libx11Quoted 4 lines
I am wondering if we should make this change in some common config metadata file to list all recipes that need this workaround untill gcc is fixed for it may be arch-powerpc.inc, since then it will be easy to remember to unbolt them once gcc is fixed.
Quoted 6 lines
I like the idea of a common include to handle this a lot better.
FWIW, I tried gcc 5 on the autobuilder. The results were 141 failures so far:
With the gcc patch I've posted applied:
so down to 57 errors. There are a few themes:
* linux-yocto 3.14 gcc5 issues
* meta-fsl-ppc and metafsl-arm gcc5 issues, particularly kernel
* poky-lsb issues with the security flags and gcc5
* x32 failed with a race of some kind in glibc, suspect transient
* gcc-target has a packaging issue which fails builds (have patch)
The good news is that the various ppc issues are fixed including the rpm one from this series.
Ross: The backports we were looking at are for warnings, not errors on the most part.
Otavio: Could you see what our options are with meta-fsl-ppc and metafsl-arm?
Cheers,
Richard
Quoted 1 line · Richard Purdie
On Sun, 2015-05-10 at 23:03 +0100, Richard Purdie wrote:
...
Quoted 2 lines
Otavio: Could you see what our options are with meta-fsl-ppc and metafsl-arm?
Yes. I foresee some challenges especially the old kernels.
fsl-arm has 2.6.35 for some platforms and fsl-ppc has 3.12.
I am adding FSL people to also take a look on these failures.
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 4 lines · Otavio Salvador
Quoted 1 line · Richard Purdie
On Sun, 2015-05-10 at 23:03 +0100, Richard Purdie wrote:
...
Quoted 8 lines
Quoted 2 lines
Otavio: Could you see what our options are with meta-fsl-ppc and metafsl-arm?
Yes. I foresee some challenges especially the old kernels.
fsl-arm has 2.6.35 for some platforms and fsl-ppc has 3.12.
I am adding FSL people to also take a look on these failures.
I found one simple hack is to set the C standard to gnu89 for kernel builds. I just added
KERNEL_CC_append = " -std=gnu89"
to my local.conf and my wandboard kernel built and booted. Haven't tried the PPC kernels yet, though.
Quoted 10 lines
--
Otavio SalvadorO.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 13 lines · Otavio Salvador
Quoted 1 line · Richard Purdie
On Sun, 2015-05-10 at 23:03 +0100, Richard Purdie wrote:
...
Quoted 2 lines
Otavio: Could you see what our options are with meta-fsl-ppc and metafsl-arm?
Yes. I foresee some challenges especially the old kernels.
fsl-arm has 2.6.35 for some platforms and fsl-ppc has 3.12.
Most of gcc5 issues are already addressed in kernel upstream so it might be that you need few back ports. but going back to 2.6.x might be daunting. There might be a lot to deal with
Quoted 7 lines
I am adding FSL people to also take a look on these failures.
--
Otavio SalvadorO.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 46 lines · Richard Purdie
Quoted 32 lines · Richard Purdie
Quoted 26 lines · Khem Raj
Quoted 15 lines · Armin Kuster
| tset.o:(.debug_loc+0xe8): undefined reference to
.LCL0' | tset.o:(.debug_loc+0xf7): undefined reference to.LCL0'thanks Khem
Signed-off-by Armin Kuster <[email protected]>--- meta/recipes-devtools/rpm/rpm_5.4.14.bb | 3 +++ 1 file changed, 3 insertions(+)meta/recipes-devtools/rpm/rpm_5.4.14.bb +0
-0meta/recipes-devtools/rpm/rpm_5.4.14.bb inherit autotools gettext · line 115
Quoted 6 lines
meta/recipes-devtools/rpm/rpm_5.4.14.bb +3
-0@@ -110,6 +110,9 @@ inherit autotools gettext acpaths = "-I ${S}/db/dist/aclocal -I ${S}/db/dist/aclocal_java" +FULL_OPTIMIZATION_powerpc_remove = "-O2" +FULL_OPTIMIZATION_append_powerpc = " -Os " +http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/master&id=741d3bf91144973d26de647039fa60b87a09edf1
fixes same issue for libx11Quoted 4 lines
I am wondering if we should make this change in some common config metadata file to list all recipes that need this workaround untill gcc is fixed for it may be arch-powerpc.inc, since then it will be easy to remember to unbolt them once gcc is fixed.
Quoted 6 lines
I like the idea of a common include to handle this a lot better.
FWIW, I tried gcc 5 on the autobuilder. The results were 141 failures so far:
With the gcc patch I've posted applied:
so down to 57 errors. There are a few themes:
Quoted 9 lines
* linux-yocto 3.14 gcc5 issues
* meta-fsl-ppc and metafsl-arm gcc5 issues, particularly kernel
* poky-lsb issues with the security flags and gcc5
* x32 failed with a race of some kind in glibc, suspect transient
* gcc-target has a packaging issue which fails builds (have patch)The good news is that the various ppc issues are fixed including the rpm one from this series.
Have you tried arm64?
kernel did not build ( as of last week) and I have not yet tried the kernel patches Khem pointed out.
- armin
Quoted 12 lines
Ross: The backports we were looking at are for warnings, not errors on the most part.
Otavio: Could you see what our options are with meta-fsl-ppc and metafsl-arm?
Cheers,
Richard
Quoted 6 lines · Richard Purdie
With the gcc patch I've posted applied:
so down to 57 errors. There are a few themes:
Quoted 8 lines
* linux-yocto 3.14 gcc5 issues
* meta-fsl-ppc and metafsl-arm gcc5 issues, particularly kernel
* poky-lsb issues with the security flags and gcc5
* x32 failed with a race of some kind in glibc, suspect transient
* gcc-target has a packaging issue which fails builds (have patch)The good news is that the various ppc issues are fixed including the rpm one from this series.
Latest run:
with 37 errors.
* linux-yocto 3.14 gcc5 issues
* meta-fsl-ppc and meta-fsl-arm gcc5 issues, particularly kernel
* poky-lsb issues with the security flags and gcc5 (elfutils, coreutils, iptables, openssl on edgerouter)
* qemuarm doesn't boot
* u-boot with beaglebone
linux-yocto 3.14 is the next thing we need to clean up to have the most impact, qemuarm not booting is the most worrying.
Cheers,
Richard
Quoted 16 lines · Richard Purdie
Quoted 6 lines · Richard Purdie
With the gcc patch I've posted applied:
so down to 57 errors. There are a few themes:
Quoted 8 lines
* linux-yocto 3.14 gcc5 issues
* meta-fsl-ppc and metafsl-arm gcc5 issues, particularly kernel
* poky-lsb issues with the security flags and gcc5
* x32 failed with a race of some kind in glibc, suspect transient
* gcc-target has a packaging issue which fails builds (have patch)The good news is that the various ppc issues are fixed including the rpm one from this series.
Quoted 7 lines
Latest run:
with 37 errors.
* linux-yocto 3.14 gcc5 issues
I guess there are patches around which I pointed out in last email which should be ported
Quoted 1 line
* meta-fsl-ppc and meta-fsl-arm gcc5 issues, particularly kernel
same as above mostly.
Quoted 2 lines
* poky-lsb issues with the security flags and gcc5 (elfutils, coreutils, iptables, openssl on edgerouter)
Those are something need fixing per package. I will look into some of those. x86-64 issues are w.r.t one particular relocation
Quoted 1 line
* qemuarm doesn't boot
I have booted several arm machines ( bbb, overo tegra ST ) using kernels ranging from 3.8 to 3.14, I believe its linux-yocto issue most probably.
Quoted 1 line
* u-boot with beaglebone
This needs patches like this one
http://patchwork.openembedded.org/patch/92425/
Quoted 4 lines
linux-yocto 3.14 is the next thing we need to clean up to have the most impact, qemuarm not booting is the most worrying.
agreed.
Quoted 6 lines
Cheers,
Richard
Quoted 20 lines · Khem Raj
Quoted 18 lines · Richard Purdie
Quoted 6 lines · Richard Purdie
With the gcc patch I've posted applied:
so down to 57 errors. There are a few themes:
Quoted 8 lines
* linux-yocto 3.14 gcc5 issues
* meta-fsl-ppc and metafsl-arm gcc5 issues, particularly kernel
* poky-lsb issues with the security flags and gcc5
* x32 failed with a race of some kind in glibc, suspect transient
* gcc-target has a packaging issue which fails builds (have patch)The good news is that the various ppc issues are fixed including the rpm one from this series.
Latest run:
Quoted 8 lines
Quoted 5 lines
with 37 errors.
* linux-yocto 3.14 gcc5 issues
I guess there are patches around which I pointed out in last email which should be ported
I believe they would be:
bebf56a kasan: enable instrumentation of global variables
5631b8f compiler/gcc4+: Remove inaccurate comment about 'asm goto' miscompiles 71458cf kernel: add support for gcc 5
just for completeness.
I will give it a shot this weekend.
- armin
Quoted 34 lines
Quoted 2 lines
* meta-fsl-ppc and meta-fsl-arm gcc5 issues, particularly kernel
same as above mostly.
Quoted 2 lines
* poky-lsb issues with the security flags and gcc5 (elfutils, coreutils, iptables, openssl on edgerouter)
Those are something need fixing per package. I will look into some of those. x86-64 issues are w.r.t one particular relocation
Quoted 1 line
* qemuarm doesn't boot
I have booted several arm machines ( bbb, overo tegra ST ) using kernels ranging from 3.8 to 3.14, I believe its linux-yocto issue most probably.
Quoted 1 line
* u-boot with beaglebone
This needs patches like this one
http://patchwork.openembedded.org/patch/92425/Quoted 4 lines
linux-yocto 3.14 is the next thing we need to clean up to have the most impact, qemuarm not booting is the most worrying.
agreed.
Quoted 6 lines
Cheers,
Richard
Quoted 40 lines · On Fri, May 15, 2015 at 12:45 PM, akuster808 <[email protected]> wrote:
Quoted 28 lines · Khem Raj
Quoted 25 lines · Richard Purdie
Quoted 8 lines · Richard Purdie
With the gcc patch I've posted applied:
so down to 57 errors. There are a few themes:
Quoted 8 lines
* linux-yocto 3.14 gcc5 issues
* meta-fsl-ppc and metafsl-arm gcc5 issues, particularly kernel
* poky-lsb issues with the security flags and gcc5
* x32 failed with a race of some kind in glibc, suspect transient
* gcc-target has a packaging issue which fails builds (have patch)The good news is that the various ppc issues are fixed including the rpm one from this series.
Latest run:
Quoted 7 lines
Quoted 3 lines
with 37 errors.
* linux-yocto 3.14 gcc5 issues
I guess there are patches around which I pointed out in last email which should be ported
Quoted 6 lines
I believe they would be:
bebf56a kasan: enable instrumentation of global variables 5631b8f compiler/gcc4+: Remove inaccurate comment about 'asm goto' miscompiles
71458cf kernel: add support for gcc 5
I'm also queueing changes for 3.19 and 3.14, so if you do have any kernel patches, feel free to fling them in my direction so we don't duplicate that effort.
Cheers,
Bruce
Quoted 51 lines
just for completeness.
I will give it a shot this weekend.
- armin
Quoted 27 lines
Quoted 2 lines
* meta-fsl-ppc and meta-fsl-arm gcc5 issues, particularly kernel
same as above mostly.
Quoted 2 lines
* poky-lsb issues with the security flags and gcc5 (elfutils, coreutils, iptables, openssl on edgerouter)
Those are something need fixing per package. I will look into some of those. x86-64 issues are w.r.t one particular relocation
Quoted 1 line
* qemuarm doesn't boot
I have booted several arm machines ( bbb, overo tegra ST ) using kernels ranging from 3.8 to 3.14, I believe its linux-yocto issue most probably.
Quoted 1 line
* u-boot with beaglebone
This needs patches like this one
http://patchwork.openembedded.org/patch/92425/Quoted 1 line
Quoted 12 lines
Quoted 3 lines
linux-yocto 3.14 is the next thing we need to clean up to have the most impact, qemuarm not booting is the most worrying.
agreed.
Quoted 7 lines
Cheers,
Richard
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
Quoted 43 lines · Bruce Ashfield
Quoted 42 lines · On Fri, May 15, 2015 at 12:45 PM, akuster808 <[email protected]> wrote:
Quoted 28 lines · Khem Raj
Quoted 25 lines · Richard Purdie
Quoted 8 lines · Richard Purdie
With the gcc patch I've posted applied:
so down to 57 errors. There are a few themes:
Quoted 8 lines
* linux-yocto 3.14 gcc5 issues
* meta-fsl-ppc and metafsl-arm gcc5 issues, particularly kernel
* poky-lsb issues with the security flags and gcc5
* x32 failed with a race of some kind in glibc, suspect transient
* gcc-target has a packaging issue which fails builds (have patch)The good news is that the various ppc issues are fixed including the rpm one from this series.
Latest run:
Quoted 7 lines
Quoted 3 lines
with 37 errors.
* linux-yocto 3.14 gcc5 issues
I guess there are patches around which I pointed out in last email which should be ported
I believe they would be:
Quoted 8 lines
Quoted 4 lines
bebf56a kasan: enable instrumentation of global variables 5631b8f compiler/gcc4+: Remove inaccurate comment about 'asm goto' miscompiles
71458cf kernel: add support for gcc 5I'm also queueing changes for 3.19 and 3.14, so if you do have any kernel patches, feel free to fling them in my direction so we don't duplicate that effort.
sure thing.
3.19 should all ready have 1458cf kernel: add support for gcc 5.
3.14 has it as well..
must be something else causing the issue.
- armin
Quoted 59 lines
Cheers,
Bruce
Quoted 51 lines
just for completeness.
I will give it a shot this weekend.
- armin
Quoted 27 lines
Quoted 2 lines
* meta-fsl-ppc and meta-fsl-arm gcc5 issues, particularly kernel
same as above mostly.
Quoted 2 lines
* poky-lsb issues with the security flags and gcc5 (elfutils, coreutils, iptables, openssl on edgerouter)
Those are something need fixing per package. I will look into some of those. x86-64 issues are w.r.t one particular relocation
Quoted 1 line
* qemuarm doesn't boot
I have booted several arm machines ( bbb, overo tegra ST ) using kernels ranging from 3.8 to 3.14, I believe its linux-yocto issue most probably.
Quoted 1 line
* u-boot with beaglebone
This needs patches like this one
http://patchwork.openembedded.org/patch/92425/Quoted 1 line
Quoted 12 lines
Quoted 3 lines
linux-yocto 3.14 is the next thing we need to clean up to have the most impact, qemuarm not booting is the most worrying.
agreed.
Quoted 7 lines
Cheers,
Richard
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 16 lines · Richard Purdie
Quoted 6 lines · Richard Purdie
With the gcc patch I've posted applied:
so down to 57 errors. There are a few themes:
Quoted 8 lines
* linux-yocto 3.14 gcc5 issues
* meta-fsl-ppc and metafsl-arm gcc5 issues, particularly kernel
* poky-lsb issues with the security flags and gcc5
* x32 failed with a race of some kind in glibc, suspect transient
* gcc-target has a packaging issue which fails builds (have patch)The good news is that the various ppc issues are fixed including the rpm one from this series.
Quoted 7 lines
Latest run:
with 37 errors.
* linux-yocto 3.14 gcc5 issues
I had a look at the failures in more detail today, and I can have a go at fixing the qemu* build failures tomorrow.
I have one patch from Armin, and will pick up some of the patches that Khem referenced in his earlier email.
.. but for the reference BSPs, I simply don't have the cycles. Can we just open bugzilla for the individual boards and get their respective maintainers to have a look ?
If this is high priority, then getting it tracked in bugzilla seems reasonable to me.
Bruce
Quoted 15 lines
* meta-fsl-ppc and meta-fsl-arm gcc5 issues, particularly kernel
* poky-lsb issues with the security flags and gcc5 (elfutils, coreutils, iptables, openssl on edgerouter)
* qemuarm doesn't boot
* u-boot with beaglebonelinux-yocto 3.14 is the next thing we need to clean up to have the most impact, qemuarm not booting is the most worrying.
Cheers,
Richard
Quoted 26 lines · Bruce Ashfield
Quoted 25 lines · Richard Purdie
Quoted 8 lines · Richard Purdie
With the gcc patch I've posted applied:
so down to 57 errors. There are a few themes:
Quoted 8 lines
* linux-yocto 3.14 gcc5 issues
* meta-fsl-ppc and metafsl-arm gcc5 issues, particularly kernel
* poky-lsb issues with the security flags and gcc5
* x32 failed with a race of some kind in glibc, suspect transient
* gcc-target has a packaging issue which fails builds (have patch)The good news is that the various ppc issues are fixed including the rpm one from this series.
Latest run:
Quoted 7 lines
Quoted 3 lines
with 37 errors.
* linux-yocto 3.14 gcc5 issues
I had a look at the failures in more detail today, and I can have a go at fixing the qemu* build failures tomorrow.
I have qemuarm building with gcc5 now (4 backports and one patch of my own), moving onto qemumips.
I'm still not planning to look at the h/w reference BSPs, so I'm looking for feedback on creating bugs and assigning them to maintainers.
Bruce
Quoted 35 lines
I have one patch from Armin, and will pick up some of the patches that Khem referenced in his earlier email.
.. but for the reference BSPs, I simply don't have the cycles. Can we just open bugzilla for the individual boards and get their respective maintainers to have a look ?
If this is high priority, then getting it tracked in bugzilla seems reasonable to me.
Bruce
Quoted 6 lines
* meta-fsl-ppc and meta-fsl-arm gcc5 issues, particularly kernel
* poky-lsb issues with the security flags and gcc5 (elfutils, coreutils, iptables, openssl on edgerouter)
* qemuarm doesn't boot
* u-boot with beagleboneQuoted 9 lines
linux-yocto 3.14 is the next thing we need to clean up to have the most impact, qemuarm not booting is the most worrying.
Cheers,
Richard
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"