All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Cc: "Ashfield, Bruce" <Bruce.Ashfield@windriver.com>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: gcc 5.2 failures
Date: Mon, 27 Jul 2015 10:30:36 +0100	[thread overview]
Message-ID: <1437989436.821.221.camel@linuxfoundation.org> (raw)

I've run a gcc 5.2 test build on the autobuilder:

http://errors.yoctoproject.org/Errors/Search/?items=10&query=3628c3c06fa4195003ac655bcc791acfac775173&limit=50

41 errors (with a few more pending).

The good news is that if we tweak the security flags, the poky-lsb gcc,
elfutils, coreutils and iptables issues can be removed and I have a
patch for this. This leaves:

3.14 kernel failures for edgerouter, genericx86-64, qemuarm, beaglebone,
mpc8315e-rdb

openssl issue for p1022ds

u-boot on imx28evk, p1022ds, mpc8315e-rdb

xf86-video-imxfb-vivante on imx6qsabresd

linux-imx issue on imx53qsb

Some kind of "random" qemu runtime issue (4 cases).

At this point I think we likely need to enter bugs into the bugzilla for
each of these. If we want to switch 1.9 to use this (which I think is
desirable), we need to get this fixed as a priority.

Bruce: How do you want to handle the 3.14 issues? Switch to 4.1? or fix
3.14?

Otavio: The freescale machines are looking unwell, can you help us make
sure the right people know about this?

Cheers,

Richard






             reply	other threads:[~2015-07-27  9:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27  9:30 Richard Purdie [this message]
2015-07-27 10:56 ` gcc 5.2 failures Mike Looijmans
2015-07-27 13:20 ` Bruce Ashfield
2015-07-27 13:24   ` Yi Qingliang
2015-07-27 13:31   ` Bruce Ashfield
2015-07-27 13:50     ` Paul Eggleton
2015-07-27 13:55       ` Bruce Ashfield
2015-07-27 13:52   ` Richard Purdie
2015-07-27 13:55     ` Bruce Ashfield
2015-08-11  0:15 ` Khem Raj

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=1437989436.821.221.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Bruce.Ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@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.