From: akuster808 <akuster808@gmail.com>
To: Khem Raj <raj.khem@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] rpm: fix build issue with gcc5
Date: Mon, 11 May 2015 09:17:15 -0700 [thread overview]
Message-ID: <5550D60B.9050707@gmail.com> (raw)
In-Reply-To: <CAMKF1sriNnycqHYmhayqaGs2pD8mKAzrd5YLBVrZei4cYW7TNQ@mail.gmail.com>
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
next prev parent reply other threads:[~2015-05-11 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 [this message]
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
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=5550D60B.9050707@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--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