From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
viro@zeniv.linux.org.uk,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: commit 4dd1837d7589f468ed109556513f476e7a7f9121 breaks build
Date: Sun, 20 Nov 2016 14:02:17 +0100 [thread overview]
Message-ID: <20161120130217.GB19562@Red> (raw)
In-Reply-To: <20161120123422.GT1041@n2100.armlinux.org.uk>
On Sun, Nov 20, 2016 at 12:34:22PM +0000, Russell King - ARM Linux wrote:
> On Sun, Nov 20, 2016 at 12:43:38PM +0100, Tobias Jakobi wrote:
> > Hello Russell,
> >
> > Russell King - ARM Linux wrote:
> > > None of the autobuilders are finding this problem, and they build a
> > > wide range of configurations. Maybe it's something specific to how
> > > you're building the kernel - can you give step by step instructions
> > > how to reproduce this please?
> > Just using plain make here, no cross-compiler or anything involved. gcc
> > is version 4.9.4.
>
> Hmm. The commit you mention was merged during the merge window, so
> anyone building 4.9-rc1 or later should be seeing this problem, but
> they aren't. I've built many kernels post -rc1, and I'm not seeing
> the problem with my 4.7.4 cross compiler.
>
I have the same issue here on all my Allwinner ARM device.
I have not reported this issue since I believed to see some report of it.
I cross compile with armv7a-hardfloat-linux-gnueabi-4.9.3.
With CONFIG_UNUSED_SYMBOLS set, the issue disapear
Regards
WARNING: multiple messages have this Message-ID (diff)
From: clabbe.montjoie@gmail.com (Corentin Labbe)
To: linux-arm-kernel@lists.infradead.org
Subject: commit 4dd1837d7589f468ed109556513f476e7a7f9121 breaks build
Date: Sun, 20 Nov 2016 14:02:17 +0100 [thread overview]
Message-ID: <20161120130217.GB19562@Red> (raw)
In-Reply-To: <20161120123422.GT1041@n2100.armlinux.org.uk>
On Sun, Nov 20, 2016 at 12:34:22PM +0000, Russell King - ARM Linux wrote:
> On Sun, Nov 20, 2016 at 12:43:38PM +0100, Tobias Jakobi wrote:
> > Hello Russell,
> >
> > Russell King - ARM Linux wrote:
> > > None of the autobuilders are finding this problem, and they build a
> > > wide range of configurations. Maybe it's something specific to how
> > > you're building the kernel - can you give step by step instructions
> > > how to reproduce this please?
> > Just using plain make here, no cross-compiler or anything involved. gcc
> > is version 4.9.4.
>
> Hmm. The commit you mention was merged during the merge window, so
> anyone building 4.9-rc1 or later should be seeing this problem, but
> they aren't. I've built many kernels post -rc1, and I'm not seeing
> the problem with my 4.7.4 cross compiler.
>
I have the same issue here on all my Allwinner ARM device.
I have not reported this issue since I believed to see some report of it.
I cross compile with armv7a-hardfloat-linux-gnueabi-4.9.3.
With CONFIG_UNUSED_SYMBOLS set, the issue disapear
Regards
next prev parent reply other threads:[~2016-11-20 13:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-20 2:47 commit 4dd1837d7589f468ed109556513f476e7a7f9121 breaks build Tobias Jakobi
2016-11-20 2:47 ` Tobias Jakobi
2016-11-20 11:30 ` Russell King - ARM Linux
2016-11-20 11:30 ` Russell King - ARM Linux
2016-11-20 11:43 ` Tobias Jakobi
2016-11-20 11:43 ` Tobias Jakobi
2016-11-20 12:34 ` Russell King - ARM Linux
2016-11-20 12:34 ` Russell King - ARM Linux
2016-11-20 12:56 ` Tobias Jakobi
2016-11-20 12:56 ` Tobias Jakobi
2016-11-20 13:25 ` Russell King - ARM Linux
2016-11-20 13:25 ` Russell King - ARM Linux
2016-11-20 17:03 ` Nicolas Pitre
2016-11-20 17:03 ` Nicolas Pitre
2016-11-20 17:22 ` Russell King - ARM Linux
2016-11-20 17:22 ` Russell King - ARM Linux
2016-11-22 11:11 ` Arnd Bergmann
2016-11-22 11:11 ` Arnd Bergmann
2016-11-20 13:02 ` Corentin Labbe [this message]
2016-11-20 13:02 ` Corentin Labbe
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=20161120130217.GB19562@Red \
--to=clabbe.montjoie@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=tjakobi@math.uni-bielefeld.de \
--cc=viro@zeniv.linux.org.uk \
/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.