* [PATCH] rpm: fix build issue with gcc5 @ 2015-05-10 14:28 Armin Kuster 2015-05-10 16:15 ` Khem Raj 0 siblings, 1 reply; 18+ messages in thread From: Armin Kuster @ 2015-05-10 14:28 UTC (permalink / raw) To: openembedded-core | 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 <akuster808@gmail.com> --- meta/recipes-devtools/rpm/rpm_5.4.14.bb | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta/recipes-devtools/rpm/rpm_5.4.14.bb b/meta/recipes-devtools/rpm/rpm_5.4.14.bb index 03a24f0..22b111a 100644 --- a/meta/recipes-devtools/rpm/rpm_5.4.14.bb +++ b/meta/recipes-devtools/rpm/rpm_5.4.14.bb @@ -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" -- 2.3.5 ^ permalink raw reply related [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-10 14:28 [PATCH] rpm: fix build issue with gcc5 Armin Kuster @ 2015-05-10 16:15 ` Khem Raj 2015-05-10 22:03 ` Richard Purdie 0 siblings, 1 reply; 18+ messages in thread From: Khem Raj @ 2015-05-10 16:15 UTC (permalink / raw) To: Armin Kuster; +Cc: Patches and discussions about the oe-core layer On Sun, May 10, 2015 at 7:28 AM, Armin Kuster <akuster808@gmail.com> wrote: > | 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 <akuster808@gmail.com> > --- > meta/recipes-devtools/rpm/rpm_5.4.14.bb | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/meta/recipes-devtools/rpm/rpm_5.4.14.bb b/meta/recipes-devtools/rpm/rpm_5.4.14.bb > index 03a24f0..22b111a 100644 > --- a/meta/recipes-devtools/rpm/rpm_5.4.14.bb > +++ b/meta/recipes-devtools/rpm/rpm_5.4.14.bb > @@ -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. > # 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 > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-10 16:15 ` Khem Raj @ 2015-05-10 22:03 ` Richard Purdie 2015-05-11 15:30 ` akuster808 ` (2 more replies) 0 siblings, 3 replies; 18+ messages in thread From: Richard Purdie @ 2015-05-10 22:03 UTC (permalink / raw) To: Khem Raj; +Cc: Patches and discussions about the oe-core layer On Sun, 2015-05-10 at 09:15 -0700, Khem Raj wrote: > On Sun, May 10, 2015 at 7:28 AM, Armin Kuster <akuster808@gmail.com> wrote: > > | 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 <akuster808@gmail.com> > > --- > > meta/recipes-devtools/rpm/rpm_5.4.14.bb | 3 +++ > > 1 file changed, 3 insertions(+) > > > > diff --git a/meta/recipes-devtools/rpm/rpm_5.4.14.bb b/meta/recipes-devtools/rpm/rpm_5.4.14.bb > > index 03a24f0..22b111a 100644 > > --- a/meta/recipes-devtools/rpm/rpm_5.4.14.bb > > +++ b/meta/recipes-devtools/rpm/rpm_5.4.14.bb > > @@ -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. 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: http://errors.yoctoproject.org/Errors/Search/?items=10&query=1426e31f0bcd19f066931d2ecbdec3752b14e88e&limit=150 Cheers, Richard ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-10 22:03 ` Richard Purdie @ 2015-05-11 15:30 ` akuster808 2015-05-11 15:47 ` Khem Raj 2015-05-12 7:06 ` Richard Purdie 2 siblings, 0 replies; 18+ messages in thread From: akuster808 @ 2015-05-11 15:30 UTC (permalink / raw) To: Richard Purdie, Khem Raj; +Cc: Patches and discussions about the oe-core layer On 05/10/2015 03:03 PM, Richard Purdie wrote: > On Sun, 2015-05-10 at 09:15 -0700, Khem Raj wrote: >> On Sun, May 10, 2015 at 7:28 AM, Armin Kuster <akuster808@gmail.com> wrote: >>> | 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 <akuster808@gmail.com> >>> --- >>> meta/recipes-devtools/rpm/rpm_5.4.14.bb | 3 +++ >>> 1 file changed, 3 insertions(+) >>> >>> diff --git a/meta/recipes-devtools/rpm/rpm_5.4.14.bb b/meta/recipes-devtools/rpm/rpm_5.4.14.bb >>> index 03a24f0..22b111a 100644 >>> --- a/meta/recipes-devtools/rpm/rpm_5.4.14.bb >>> +++ b/meta/recipes-devtools/rpm/rpm_5.4.14.bb >>> @@ -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. > > I like the idea of a common include to handle this a lot better. Second that. I will send a patch - armin > > FWIW, I tried gcc 5 on the autobuilder. The results were 141 failures so > far: > > http://errors.yoctoproject.org/Errors/Search/?items=10&query=1426e31f0bcd19f066931d2ecbdec3752b14e88e&limit=150 > > Cheers, > > Richard > ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-10 22:03 ` Richard Purdie 2015-05-11 15:30 ` akuster808 @ 2015-05-11 15:47 ` Khem Raj 2015-05-11 16:17 ` akuster808 2015-05-12 7:06 ` Richard Purdie 2 siblings, 1 reply; 18+ messages in thread From: Khem Raj @ 2015-05-11 15:47 UTC (permalink / raw) To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer On Sun, May 10, 2015 at 3:03 PM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote: > 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: > > http://errors.yoctoproject.org/Errors/Search/?items=10&query=1426e31f0bcd19f066931d2ecbdec3752b14e88e&limit=150 > 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 > Cheers, > > Richard ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-11 15:47 ` Khem Raj @ 2015-05-11 16:17 ` akuster808 0 siblings, 0 replies; 18+ messages in thread From: akuster808 @ 2015-05-11 16:17 UTC (permalink / raw) To: Khem Raj, Richard Purdie; +Cc: Patches and discussions about the oe-core layer On 05/11/2015 08:47 AM, Khem Raj wrote: > On Sun, May 10, 2015 at 3:03 PM, Richard Purdie > <richard.purdie@linuxfoundation.org> wrote: >> 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: >> >> http://errors.yoctoproject.org/Errors/Search/?items=10&query=1426e31f0bcd19f066931d2ecbdec3752b14e88e&limit=150 >> > > 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 arm64 kernel build failed don't recall how many packages. - armin > >> Cheers, >> >> Richard ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-10 22:03 ` Richard Purdie 2015-05-11 15:30 ` akuster808 2015-05-11 15:47 ` Khem Raj @ 2015-05-12 7:06 ` Richard Purdie 2015-05-12 14:57 ` Otavio Salvador ` (2 more replies) 2 siblings, 3 replies; 18+ messages in thread From: Richard Purdie @ 2015-05-12 7:06 UTC (permalink / raw) To: Khem Raj; +Cc: Otavio Salvador, Patches and discussions about the oe-core layer On Sun, 2015-05-10 at 23:03 +0100, Richard Purdie wrote: > On Sun, 2015-05-10 at 09:15 -0700, Khem Raj wrote: > > On Sun, May 10, 2015 at 7:28 AM, Armin Kuster <akuster808@gmail.com> wrote: > > > | 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 <akuster808@gmail.com> > > > --- > > > meta/recipes-devtools/rpm/rpm_5.4.14.bb | 3 +++ > > > 1 file changed, 3 insertions(+) > > > > > > diff --git a/meta/recipes-devtools/rpm/rpm_5.4.14.bb b/meta/recipes-devtools/rpm/rpm_5.4.14.bb > > > index 03a24f0..22b111a 100644 > > > --- a/meta/recipes-devtools/rpm/rpm_5.4.14.bb > > > +++ b/meta/recipes-devtools/rpm/rpm_5.4.14.bb > > > @@ -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. > > 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: > > http://errors.yoctoproject.org/Errors/Search/?items=10&query=1426e31f0bcd19f066931d2ecbdec3752b14e88e&limit=150 With the gcc patch I've posted applied: http://errors.yoctoproject.org/Errors/Search/?items=10&query=5fd0b7c163f4f3312bea9bd3246a6bd67a8da594&limit=100 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 ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-12 7:06 ` Richard Purdie @ 2015-05-12 14:57 ` Otavio Salvador 2015-05-12 15:15 ` Dan McGregor 2015-05-12 16:11 ` Khem Raj 2015-05-12 16:17 ` akuster808 2015-05-15 10:40 ` Richard Purdie 2 siblings, 2 replies; 18+ messages in thread From: Otavio Salvador @ 2015-05-12 14:57 UTC (permalink / raw) To: Richard Purdie Cc: Richard Schmitt, Patches and discussions about the oe-core layer On Tue, May 12, 2015 at 4:06 AM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote: > On Sun, 2015-05-10 at 23:03 +0100, Richard Purdie wrote: ... > 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. -- 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 ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-12 14:57 ` Otavio Salvador @ 2015-05-12 15:15 ` Dan McGregor 2015-05-12 16:11 ` Khem Raj 1 sibling, 0 replies; 18+ messages in thread From: Dan McGregor @ 2015-05-12 15:15 UTC (permalink / raw) To: Otavio Salvador Cc: Patches and discussions about the oe-core layer, Richard Schmitt On 12 May 2015 at 08:57, Otavio Salvador <otavio@ossystems.com.br> wrote: > On Tue, May 12, 2015 at 4:06 AM, Richard Purdie > <richard.purdie@linuxfoundation.org> wrote: >> On Sun, 2015-05-10 at 23:03 +0100, Richard Purdie wrote: > ... >> 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. > > -- > 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 > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-12 14:57 ` Otavio Salvador 2015-05-12 15:15 ` Dan McGregor @ 2015-05-12 16:11 ` Khem Raj 1 sibling, 0 replies; 18+ messages in thread From: Khem Raj @ 2015-05-12 16:11 UTC (permalink / raw) To: Otavio Salvador Cc: Richard Schmitt, Patches and discussions about the oe-core layer [-- Attachment #1: Type: text/plain, Size: 936 bytes --] > On May 12, 2015, at 7:57 AM, Otavio Salvador <otavio@ossystems.com.br> wrote: > > On Tue, May 12, 2015 at 4:06 AM, Richard Purdie > <richard.purdie@linuxfoundation.org> wrote: >> On Sun, 2015-05-10 at 23:03 +0100, Richard Purdie wrote: > ... >> 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 > > I am adding FSL people to also take a look on these failures. > > -- > 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 [-- Attachment #2: Message signed with OpenPGP using GPGMail --] [-- Type: application/pgp-signature, Size: 211 bytes --] ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-12 7:06 ` Richard Purdie 2015-05-12 14:57 ` Otavio Salvador @ 2015-05-12 16:17 ` akuster808 2015-05-15 10:40 ` Richard Purdie 2 siblings, 0 replies; 18+ messages in thread From: akuster808 @ 2015-05-12 16:17 UTC (permalink / raw) To: Richard Purdie, Khem Raj Cc: Otavio Salvador, Patches and discussions about the oe-core layer On 05/12/2015 12:06 AM, Richard Purdie wrote: > On Sun, 2015-05-10 at 23:03 +0100, Richard Purdie wrote: >> On Sun, 2015-05-10 at 09:15 -0700, Khem Raj wrote: >>> On Sun, May 10, 2015 at 7:28 AM, Armin Kuster <akuster808@gmail.com> wrote: >>>> | 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 <akuster808@gmail.com> >>>> --- >>>> meta/recipes-devtools/rpm/rpm_5.4.14.bb | 3 +++ >>>> 1 file changed, 3 insertions(+) >>>> >>>> diff --git a/meta/recipes-devtools/rpm/rpm_5.4.14.bb b/meta/recipes-devtools/rpm/rpm_5.4.14.bb >>>> index 03a24f0..22b111a 100644 >>>> --- a/meta/recipes-devtools/rpm/rpm_5.4.14.bb >>>> +++ b/meta/recipes-devtools/rpm/rpm_5.4.14.bb >>>> @@ -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. >> >> 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: >> >> http://errors.yoctoproject.org/Errors/Search/?items=10&query=1426e31f0bcd19f066931d2ecbdec3752b14e88e&limit=150 > > With the gcc patch I've posted applied: > > http://errors.yoctoproject.org/Errors/Search/?items=10&query=5fd0b7c163f4f3312bea9bd3246a6bd67a8da594&limit=100 > > 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. > 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 > 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 > > > ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-12 7:06 ` Richard Purdie 2015-05-12 14:57 ` Otavio Salvador 2015-05-12 16:17 ` akuster808 @ 2015-05-15 10:40 ` Richard Purdie 2015-05-15 16:25 ` Khem Raj 2015-05-19 20:50 ` Bruce Ashfield 2 siblings, 2 replies; 18+ messages in thread From: Richard Purdie @ 2015-05-15 10:40 UTC (permalink / raw) To: Khem Raj; +Cc: Otavio Salvador, Patches and discussions about the oe-core layer On Tue, 2015-05-12 at 08:06 +0100, Richard Purdie wrote: > With the gcc patch I've posted applied: > > http://errors.yoctoproject.org/Errors/Search/?items=10&query=5fd0b7c163f4f3312bea9bd3246a6bd67a8da594&limit=100 > > 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. Latest run: http://errors.yoctoproject.org/Errors/Search/?items=10&query=a2fbb1b6b6e564b3f9d40550c0b408978f420039&limit=100 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 ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-15 10:40 ` Richard Purdie @ 2015-05-15 16:25 ` Khem Raj 2015-05-15 16:45 ` akuster808 2015-05-19 20:50 ` Bruce Ashfield 1 sibling, 1 reply; 18+ messages in thread From: Khem Raj @ 2015-05-15 16:25 UTC (permalink / raw) To: Richard Purdie Cc: Otavio Salvador, Patches and discussions about the oe-core layer On Fri, May 15, 2015 at 3:40 AM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote: > On Tue, 2015-05-12 at 08:06 +0100, Richard Purdie wrote: >> With the gcc patch I've posted applied: >> >> http://errors.yoctoproject.org/Errors/Search/?items=10&query=5fd0b7c163f4f3312bea9bd3246a6bd67a8da594&limit=100 >> >> 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. > > Latest run: > > http://errors.yoctoproject.org/Errors/Search/?items=10&query=a2fbb1b6b6e564b3f9d40550c0b408978f420039&limit=100 > > 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 > * meta-fsl-ppc and meta-fsl-arm gcc5 issues, particularly kernel same as above mostly. > * 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 > * 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. > * u-boot with beaglebone This needs patches like this one http://patchwork.openembedded.org/patch/92425/ > > 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. > Cheers, > > Richard > > > ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-15 16:25 ` Khem Raj @ 2015-05-15 16:45 ` akuster808 2015-05-15 16:48 ` Bruce Ashfield 0 siblings, 1 reply; 18+ messages in thread From: akuster808 @ 2015-05-15 16:45 UTC (permalink / raw) To: Khem Raj, Richard Purdie Cc: Otavio Salvador, Patches and discussions about the oe-core layer On 05/15/2015 09:25 AM, Khem Raj wrote: > On Fri, May 15, 2015 at 3:40 AM, Richard Purdie > <richard.purdie@linuxfoundation.org> wrote: >> On Tue, 2015-05-12 at 08:06 +0100, Richard Purdie wrote: >>> With the gcc patch I've posted applied: >>> >>> http://errors.yoctoproject.org/Errors/Search/?items=10&query=5fd0b7c163f4f3312bea9bd3246a6bd67a8da594&limit=100 >>> >>> 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. >> >> Latest run: >> >> http://errors.yoctoproject.org/Errors/Search/?items=10&query=a2fbb1b6b6e564b3f9d40550c0b408978f420039&limit=100 >> >> 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 > >> * meta-fsl-ppc and meta-fsl-arm gcc5 issues, particularly kernel > > same as above mostly. > >> * 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 > >> * 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. > >> * u-boot with beaglebone > > This needs patches like this one > http://patchwork.openembedded.org/patch/92425/ > >> >> 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. >> Cheers, >> >> Richard >> >> >> ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-15 16:45 ` akuster808 @ 2015-05-15 16:48 ` Bruce Ashfield 2015-05-15 20:00 ` akuster808 0 siblings, 1 reply; 18+ messages in thread From: Bruce Ashfield @ 2015-05-15 16:48 UTC (permalink / raw) To: akuster808 Cc: Otavio Salvador, Patches and discussions about the oe-core layer On Fri, May 15, 2015 at 12:45 PM, akuster808 <akuster808@gmail.com> wrote: > > > On 05/15/2015 09:25 AM, Khem Raj wrote: >> >> On Fri, May 15, 2015 at 3:40 AM, Richard Purdie >> <richard.purdie@linuxfoundation.org> wrote: >>> >>> On Tue, 2015-05-12 at 08:06 +0100, Richard Purdie wrote: >>>> >>>> With the gcc patch I've posted applied: >>>> >>>> >>>> http://errors.yoctoproject.org/Errors/Search/?items=10&query=5fd0b7c163f4f3312bea9bd3246a6bd67a8da594&limit=100 >>>> >>>> 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. >>> >>> >>> Latest run: >>> >>> >>> http://errors.yoctoproject.org/Errors/Search/?items=10&query=a2fbb1b6b6e564b3f9d40550c0b408978f420039&limit=100 >>> >>> 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 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 > > just for completeness. > > I will give it a shot this weekend. > > - armin > >> >>> * meta-fsl-ppc and meta-fsl-arm gcc5 issues, particularly kernel >> >> >> same as above mostly. >> >>> * 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 >> >>> * 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. >> >>> * u-boot with beaglebone >> >> >> This needs patches like this one >> http://patchwork.openembedded.org/patch/92425/ >> >>> >>> 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. >>> >>> Cheers, >>> >>> Richard >>> >>> >>> > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-15 16:48 ` Bruce Ashfield @ 2015-05-15 20:00 ` akuster808 0 siblings, 0 replies; 18+ messages in thread From: akuster808 @ 2015-05-15 20:00 UTC (permalink / raw) To: Bruce Ashfield Cc: Otavio Salvador, Patches and discussions about the oe-core layer On 05/15/2015 09:48 AM, Bruce Ashfield wrote: > On Fri, May 15, 2015 at 12:45 PM, akuster808 <akuster808@gmail.com> wrote: >> >> >> On 05/15/2015 09:25 AM, Khem Raj wrote: >>> >>> On Fri, May 15, 2015 at 3:40 AM, Richard Purdie >>> <richard.purdie@linuxfoundation.org> wrote: >>>> >>>> On Tue, 2015-05-12 at 08:06 +0100, Richard Purdie wrote: >>>>> >>>>> With the gcc patch I've posted applied: >>>>> >>>>> >>>>> http://errors.yoctoproject.org/Errors/Search/?items=10&query=5fd0b7c163f4f3312bea9bd3246a6bd67a8da594&limit=100 >>>>> >>>>> 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. >>>> >>>> >>>> Latest run: >>>> >>>> >>>> http://errors.yoctoproject.org/Errors/Search/?items=10&query=a2fbb1b6b6e564b3f9d40550c0b408978f420039&limit=100 >>>> >>>> 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 > > 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. 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 > > Cheers, > > Bruce > >> >> just for completeness. >> >> I will give it a shot this weekend. >> >> - armin >> >>> >>>> * meta-fsl-ppc and meta-fsl-arm gcc5 issues, particularly kernel >>> >>> >>> same as above mostly. >>> >>>> * 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 >>> >>>> * 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. >>> >>>> * u-boot with beaglebone >>> >>> >>> This needs patches like this one >>> http://patchwork.openembedded.org/patch/92425/ >>> >>>> >>>> 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. >>>> >>>> Cheers, >>>> >>>> Richard >>>> >>>> >>>> >> -- >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-core > > > ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-15 10:40 ` Richard Purdie 2015-05-15 16:25 ` Khem Raj @ 2015-05-19 20:50 ` Bruce Ashfield 2015-05-20 20:42 ` Bruce Ashfield 1 sibling, 1 reply; 18+ messages in thread From: Bruce Ashfield @ 2015-05-19 20:50 UTC (permalink / raw) To: Richard Purdie, Khem Raj Cc: Otavio Salvador, Patches and discussions about the oe-core layer On 2015-05-15 06:40 AM, Richard Purdie wrote: > On Tue, 2015-05-12 at 08:06 +0100, Richard Purdie wrote: >> With the gcc patch I've posted applied: >> >> http://errors.yoctoproject.org/Errors/Search/?items=10&query=5fd0b7c163f4f3312bea9bd3246a6bd67a8da594&limit=100 >> >> 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. > > Latest run: > > http://errors.yoctoproject.org/Errors/Search/?items=10&query=a2fbb1b6b6e564b3f9d40550c0b408978f420039&limit=100 > > 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 > * 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 > > > ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH] rpm: fix build issue with gcc5 2015-05-19 20:50 ` Bruce Ashfield @ 2015-05-20 20:42 ` Bruce Ashfield 0 siblings, 0 replies; 18+ messages in thread From: Bruce Ashfield @ 2015-05-20 20:42 UTC (permalink / raw) To: Richard Purdie, Khem Raj Cc: Otavio Salvador, Patches and discussions about the oe-core layer On Tue, May 19, 2015 at 4:50 PM, Bruce Ashfield <bruce.ashfield@windriver.com> wrote: > On 2015-05-15 06:40 AM, Richard Purdie wrote: >> >> On Tue, 2015-05-12 at 08:06 +0100, Richard Purdie wrote: >>> >>> With the gcc patch I've posted applied: >>> >>> >>> http://errors.yoctoproject.org/Errors/Search/?items=10&query=5fd0b7c163f4f3312bea9bd3246a6bd67a8da594&limit=100 >>> >>> 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. >> >> >> Latest run: >> >> >> http://errors.yoctoproject.org/Errors/Search/?items=10&query=a2fbb1b6b6e564b3f9d40550c0b408978f420039&limit=100 >> >> 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 > > 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 > > >> * 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 >> >> >> > > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2015-05-20 20:42 UTC | newest] Thread overview: 18+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2015-05-10 14:28 [PATCH] rpm: fix build issue with gcc5 Armin Kuster 2015-05-10 16:15 ` Khem Raj 2015-05-10 22:03 ` Richard Purdie 2015-05-11 15:30 ` akuster808 2015-05-11 15:47 ` Khem Raj 2015-05-11 16:17 ` akuster808 2015-05-12 7:06 ` Richard Purdie 2015-05-12 14:57 ` Otavio Salvador 2015-05-12 15:15 ` Dan McGregor 2015-05-12 16:11 ` Khem Raj 2015-05-12 16:17 ` akuster808 2015-05-15 10:40 ` Richard Purdie 2015-05-15 16:25 ` Khem Raj 2015-05-15 16:45 ` akuster808 2015-05-15 16:48 ` Bruce Ashfield 2015-05-15 20:00 ` akuster808 2015-05-19 20:50 ` Bruce Ashfield 2015-05-20 20:42 ` Bruce Ashfield
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox