From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: omap2plus_defconfig not building
Date: Fri, 26 Nov 2010 11:45:09 +0000 [thread overview]
Message-ID: <20101126114509.GL9310@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4CEF9B8D.3010106@ti.com>
On Fri, Nov 26, 2010 at 05:05:41PM +0530, Anand Gadiyar wrote:
> On 11/25/2010 10:20 PM, Russell King - ARM Linux wrote:
> > Please do:
> >
> > make V=1 CFLAGS_KERNEL=-v arch/arm/kernel/swp_emulate.o
> >
> > and send the output. This should show what command arguments are being
> > passed to the assembler.
>
> Here's the last line of output from the command above. I've attached the
> complete log if anyone's interested.
>
> /db/omapts/arm-2010q1/bin/../lib/gcc/arm-none-linux-gnueabi/4.4.1/../../../../arm-none-linux-gnueabi/bin/as -v -I/home/userdata/a0393673/mainline/mainline/arch/arm/include -Iinclude -Iarch/arm/mach-omap2/include -Iarch/arm/plat-omap/include -EL -march=armv6 -mfloat-abi=soft -meabi=5 -march=armv7-a -o /tmp/a0393673/ccache/tmp.hash.ubomapldc13.24604.o /tmp/cc4MQyRN.s
> GNU assembler version 2.19.51 (arm-none-linux-gnueabi) using BFD version (Sourcery G++ Lite 2010q1-202) 2.19.51.20090709
> /tmp/cc4MQyRN.s: Assembler messages:
> /tmp/cc4MQyRN.s:339: Error: selected processor does not support ARM mode `ldrexb r7,[r6]'
> /tmp/cc4MQyRN.s:340: Error: selected processor does not support ARM mode `strexb r3,r2,[r6]'
> make[1]: *** [arch/arm/kernel/swp_emulate.o] Error 1
> make: *** [arch/arm/kernel/swp_emulate.o] Error 2
$ arm-linux-as -v -o /dev/null /dev/null
GNU assembler version 2.19.1 (arm-linux) using BFD version (GNU Binutils) 2.19.1
$ arm-linux-as -march=armv6 -mfloat-abi=soft -meabi=5 -march=armv7-a -o /dev/null t.s
$ arm-linux-as -march=armv6 -mfloat-abi=soft -meabi=5 -o /dev/null t.s
t.s: Assembler messages:
t.s:1: Error: selected processor does not support `ldrexb r7,[r6]'
So it looks like someone's changed the behaviour of the assembler so it's
no longer possible to override the -march= argument from the gcc frontend.
Maybe Will can shed some light on this?
next prev parent reply other threads:[~2010-11-26 11:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 10:18 linux-next: omap2plus_defconfig not building Anand Gadiyar
2010-10-19 11:37 ` Catalin Marinas
2010-10-19 12:14 ` Anand Gadiyar
2010-10-19 22:49 ` Tony Lindgren
2010-11-08 6:05 ` Anand Gadiyar
2010-11-08 9:38 ` Uwe Kleine-König
2010-11-08 9:48 ` Catalin Marinas
2010-11-08 10:14 ` Russell King - ARM Linux
2010-11-08 10:20 ` Catalin Marinas
2010-11-08 10:25 ` Russell King - ARM Linux
2010-11-08 10:31 ` Catalin Marinas
2010-11-25 13:54 ` Anand Gadiyar
2010-11-25 16:50 ` Russell King - ARM Linux
2010-11-26 11:35 ` Anand Gadiyar
2010-11-26 11:45 ` Russell King - ARM Linux [this message]
2010-11-26 12:22 ` Will Deacon
2010-11-26 12:28 ` Russell King - ARM Linux
2010-11-26 12:38 ` Catalin Marinas
2010-11-26 12:55 ` Dave Martin
2010-11-26 13:00 ` Russell King - ARM Linux
2010-11-26 13:31 ` Dave Martin
2010-11-26 13:53 ` Russell King - ARM Linux
2010-11-26 12:33 ` Russell King - ARM Linux
2010-12-23 19:55 ` Tony Lindgren
2010-12-23 20:15 ` Tony Lindgren
2010-12-23 20:30 ` Russell King - ARM Linux
2010-12-23 21:06 ` Tony Lindgren
2011-01-07 3:59 ` Tony Lindgren
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=20101126114509.GL9310@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).