From: gadiyar@ti.com (Anand Gadiyar)
To: linux-arm-kernel@lists.infradead.org
Subject: Build breakage with omap2plus_defconfig
Date: Fri, 7 Jan 2011 18:20:43 +0530 [thread overview]
Message-ID: <d36c47cf71accc194040e98d74f768c0@mail.gmail.com> (raw)
In-Reply-To: <20110107123859.GA9592@legolas.emea.dhcp.ti.com>
Felipe Balbi wrote:
> Hi all,
>
> Today's Linus' tree
> (01539ba2a706ab7d35fc0667dff919ade7f87d63) fails to
> build with omap2plus_defconfig:
>
> $ crossmake
> CHK include/linux/version.h
> CHK include/generated/utsrelease.h
> make[1]: `include/generated/mach-types.h' is up to date.
> CALL scripts/checksyscalls.sh
> CHK include/generated/compile.h
> CC arch/arm/kernel/swp_emulate.o
> /tmp/cc2V7p5j.s: Assembler messages:
> /tmp/cc2V7p5j.s:161: Error: selected processor does not support ARM mode
`ldrexb r3,[r4]'
> /tmp/cc2V7p5j.s:162: Error: selected processor does not support ARM mode
`strexb r0,r2,[r4]'
> make[1]: *** [arch/arm/kernel/swp_emulate.o] Error 1
> make: *** [arch/arm/kernel] Error 2
I haven't found a way around this other than to turn off
CONFIG_SWP_EMULATE. Here's a patch doing that [1].
The discussion thread is here [2].
- Anand
[1] http://marc.info/?l=linux-omap&m=129140165126953&w=2
[2] http://marc.info/?t=128748412500003&r=1&w=2
next prev parent reply other threads:[~2011-01-07 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 12:38 Build breakage with omap2plus_defconfig Felipe Balbi
2011-01-07 12:44 ` Felipe Balbi
2011-01-07 12:48 ` Santosh Shilimkar
2011-01-07 12:59 ` Felipe Balbi
2011-01-07 13:05 ` Santosh Shilimkar
2011-01-07 13:10 ` Felipe Balbi
2011-01-07 12:50 ` Anand Gadiyar [this message]
2011-01-07 12:57 ` Felipe Balbi
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=d36c47cf71accc194040e98d74f768c0@mail.gmail.com \
--to=gadiyar@ti.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