From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] shmobile build failure
Date: Thu, 2 Jan 2014 23:23:25 +0000 [thread overview]
Message-ID: <20140102232325.GF7383@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOesGMh=uWi1gmb_1qhuF42d7Rt85RstvDmPVY2F3_YfkX9xTw@mail.gmail.com>
On Thu, Jan 02, 2014 at 03:20:36PM -0800, Olof Johansson wrote:
> On Thu, Jan 2, 2014 at 1:47 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > On Thu, Jan 02, 2014 at 09:36:07AM -0800, Olof Johansson wrote:
> >> On Thu, Jan 2, 2014 at 9:24 AM, Russell King - ARM Linux
> >> <linux@arm.linux.org.uk> wrote:
> >> > allmodconfig and allyesconfig fail with this error:
> >> >
> >> > arch/arm/mach-shmobile/setup-rcar-gen2.c:21:32: fatal error: linux/clk/shmobile.h: No such file or directory
> >> >
> >> > My guess is that shmobile on its own doesn't build because of this.
> >> > Is there a screwed dependency between arm-soc and the clk git trees?
> >>
> >> Yeah, I noticed this too but hadn't had a chance to report it yet --
> >> holidays followed by getting sick.
> >>
> >> I'm guessing they have a dependency on clk rework that we haven't merged.
> >
> > Have you run any allmod or allyesconfig builds recently? The logs from
> > those builds are excessively big and unreadable due to this:
> >
> > warning: __mcount_loc already exists: object-file.o
> >
> > being spat out for every object file being built, and I can't figure out
> > what's causing that.
>
>
> Hm, no I have not. Do you have a feel for when it began? I can do a bisect.
I don't know - I've only recently re-enabled those builds. There's
suggestions from other architectures that it may be toolchain related -
some people have blamed binutils for it, but I'm running binutils 2.22.
Hence why I'm interested if others see this too.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
next prev parent reply other threads:[~2014-01-02 23:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 17:24 [BUG] shmobile build failure Russell King - ARM Linux
2014-01-02 17:36 ` Olof Johansson
2014-01-02 21:47 ` Russell King - ARM Linux
2014-01-02 23:20 ` Olof Johansson
2014-01-02 23:23 ` Russell King - ARM Linux [this message]
2014-01-03 14:49 ` Arnd Bergmann
2014-01-03 23:39 ` Simon Horman
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=20140102232325.GF7383@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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 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).