All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Heads up on gcc 5.X issues for meta-fsl-arm and meta-fsl-ppc
Date: Mon, 27 Jul 2015 22:38:15 +0100	[thread overview]
Message-ID: <1438033095.821.291.camel@linuxfoundation.org> (raw)

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:

p1022ds:
  openssl failures (caused by patches in meta-fsl-ppc)
  u-boot-qoriq

imx28evk:
  u-boot-fslc-v2015.07+gitAUTOINC+31851bd6bd-r0 

imx53qsb:
  linux-imx

imx6qsabresd:
  xf86-video-imxfb-vivante 

I'm not going to send out any more mails about these, its really up the
the people involved with these layers to track this and come up with a
plan to sort this out. If we switch and things are failing with no sign
of them being fixed we'll have to take  action of some kind.

Cheers,

Richard



             reply	other threads:[~2015-07-27 21:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 21:38 Richard Purdie [this message]
2015-07-28  3:10 ` Heads up on gcc 5.X issues for meta-fsl-arm and meta-fsl-ppc 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
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=1438033095.821.291.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=meta-freescale@yoctoproject.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 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.