linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@linaro.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUILD BROKEN] Current Linus' master and -next don't build for imx_v6_v7_defconfig
Date: Fri, 18 Oct 2013 08:14:36 -0700	[thread overview]
Message-ID: <CAGa+x86+qfWBou2jkEjz10ix95m89cxnyyFOPwryF27YezeoPw@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1310181632160.9158@axis700.grange>

On Fri, Oct 18, 2013 at 7:59 AM, Guennadi Liakhovetski
<g.liakhovetski@gmx.de> wrote:

> On current Linus' tree as of 04919af as well as -next since 16.10, IIRC,
> compilation is broken for i.MX3*, including the default
> imx_v6_v7_defconfig. The toolchain used is
>
> arm-none-linux-gnueabi-gcc (Sourcery CodeBench Lite 2012.09-64) 4.7.2

Just for another data point, I'm not seeing this in my builds
(arm-linux-gnueabi-gcc (Ubuntu/Linaro 4.7.2-1ubuntu1) 4.7.2) and we're
not seeing this in Olof's autobuilds either for latest mainline[1] or
latest next-thierry[2].  I belive Olof is using vanilla gcc 4.8.1.

Kevin

[1] http://lists.linaro.org/pipermail/kernel-build-reports/2013-October/000721.html
[2] http://lists.linaro.org/pipermail/kernel-build-reports/2013-October/000718.html

  reply	other threads:[~2013-10-18 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 14:59 [BUILD BROKEN] Current Linus' master and -next don't build for imx_v6_v7_defconfig Guennadi Liakhovetski
2013-10-18 15:14 ` Kevin Hilman [this message]
2013-10-18 16:49   ` Guenter Roeck

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=CAGa+x86+qfWBou2jkEjz10ix95m89cxnyyFOPwryF27YezeoPw@mail.gmail.com \
    --to=khilman@linaro.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).