From: richardcochran@gmail.com (Richard Cochran)
To: linux-arm-kernel@lists.infradead.org
Subject: omap2plus_defconfig build failure in v3.12
Date: Wed, 6 Nov 2013 16:00:15 +0100 [thread overview]
Message-ID: <20131106150015.GA20674@netboy> (raw)
Will,
I am suspecting 6abdd491 "ARM: mm: use inner-shareable barriers for
TLB and user cache operations" or the commits just before as the cause
of the following build failure using the omap2plus_defconfig with
kernel v3.12.
AS arch/arm/mm/cache-v7.o
/home/richard/git/linux/arch/arm/mm/cache-v7.S: Assembler messages:
/home/richard/git/linux/arch/arm/mm/cache-v7.S:285: Error: garbage following instruction -- `dsb ishst'
/home/richard/git/linux/arch/arm/mm/cache-v7.S:297: Error: garbage following instruction -- `dsb ishst'
make[2]: *** [arch/arm/mm/cache-v7.o] Error 1
make[1]: *** [arch/arm/mm] Error 2
make: *** [sub-make] Error 2
Your commit 6abdd491 also doesn't build, but v3.11-rc4, just a few
commits preceeding, does build. I am using:
{CROSS_COMPILE}gcc --version
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q1-203) 4.3.3
Is my toolchain too old, or what is going on here?
Thanks,
Richard
next reply other threads:[~2013-11-06 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 15:00 Richard Cochran [this message]
2013-11-06 15:02 ` omap2plus_defconfig build failure in v3.12 Russell King - ARM Linux
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=20131106150015.GA20674@netboy \
--to=richardcochran@gmail.com \
--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).