From: Trevor Woerner <twoerner@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: Heads up on gcc 5.X issues for meta-fsl-arm and meta-fsl-ppc
Date: Thu, 6 Aug 2015 14:08:52 -0400 [thread overview]
Message-ID: <55C3A2B4.9060101@gmail.com> (raw)
In-Reply-To: <CAP9ODKqNQUpCaH9WrCBAhDXmy0X5a9EE=vSvPe4dy2JmREWDrw@mail.gmail.com>
On 08/06/15 09:10, Otavio Salvador wrote:
> On Thu, Aug 6, 2015 at 10:07 AM, Trevor Woerner <twoerner@gmail.com> wrote:
>> On 07/27/15 17:38, Richard Purdie wrote:
>>> It appears that gcc 5.x is going to cause a few issues for meta-fsl-arm
>>> and meta-fsl-ppc. Many of the remaining issues are specific to these
>>> layers.
>>>
>>> http://errors.yoctoproject.org/Errors/Search/?items=10&query=00957782f4dec7f39b79211e6a2a2bea6f14d2a0&limit=50
>>>
>>> is a complete list for one of the last builds. The gcc, elfutils,
>>> coreutils and iptables issues are resolved.
>>>
>>> What worries me specifically are:
>>>
>> ...
>>> imx53qsb:
>>> linux-imx
>>
>> I'm taking a look at this.
>
> I merged today the removal of i.MX5 using the linux-imx kernel. If you
> commit to support the kernel than we can revisit it but otherwise
> using mainline is the best route.
Ok, thanks.
next prev parent reply other threads:[~2015-08-06 18:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 21:38 Heads up on gcc 5.X issues for meta-fsl-arm and meta-fsl-ppc Richard Purdie
2015-07-28 3:10 ` Luo Zhenhua
2015-07-28 17:18 ` Otavio Salvador
2015-07-28 18:30 ` Otavio Salvador
2015-08-06 13:07 ` Trevor Woerner
2015-08-06 13:10 ` Otavio Salvador
2015-08-06 18:08 ` Trevor Woerner [this message]
2015-08-07 13:40 ` Trevor Woerner
2015-08-07 13:54 ` Otavio Salvador
2015-08-07 14:36 ` Richard Purdie
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=55C3A2B4.9060101@gmail.com \
--to=twoerner@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.