From: Bruce Ashfield <bruce.ashfield@windriver.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, 19 May 2015 16:50:06 -0400 [thread overview]
Message-ID: <555BA1FE.5000402@windriver.com> (raw)
In-Reply-To: <1431686433.18723.22.camel@linuxfoundation.org>
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
>
>
>
next prev parent reply other threads:[~2015-05-19 20:50 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
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 [this message]
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=555BA1FE.5000402@windriver.com \
--to=bruce.ashfield@windriver.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