Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	 Khem Raj <raj.khem@gmail.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] rpm: fix build issue with gcc5
Date: Tue, 12 May 2015 09:17:44 -0700	[thread overview]
Message-ID: <555227A8.8040309@gmail.com> (raw)
In-Reply-To: <1431414393.30971.109.camel@linuxfoundation.org>



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
>
>
>


  parent reply	other threads:[~2015-05-12 16:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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

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=555227A8.8040309@gmail.com \
    --to=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=raj.khem@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox