From: Robert Berger <gmane@reliableembeddedsystems.com>
To: poky@pokylinux.org
Subject: Re: Third party toolchain, kernel, bootloader
Date: Mon, 09 May 2011 23:21:45 +0300 [thread overview]
Message-ID: <iq9icp$d63$1@dough.gmane.org> (raw)
In-Reply-To: <36510365-CB0D-47CE-B420-56E60650019D@dominion.thruhere.net>
Hi Koen,
On 05/09/2011 08:57 PM, Koen Kooi wrote:
>> CC arch/arm/kernel/sysfs_v7.o
>> /tmp/ccFfYvGD.s: Assembler messages:
>> /tmp/ccFfYvGD.s:264: Error: selected processor does not support ARM mode
>> `smc #0'
>> /tmp/ccFfYvGD.s:306: Error: selected processor does not support ARM mode
>> `smc #0'
>> make[1]: *** [arch/arm/kernel/sysfs_v7.o] Error 1
>> make: *** [arch/arm/kernel] Error 2
>> make: *** Waiting for unfinished jobs....
>
> That's a 'feature' of binutils 2.21, either switch to 2.20 or do something like http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/commit/?id=579d8efb3eb25b114de2640d98a511893d2f4841
I tried something like this in /arch/arm/kernel/Makefile:
plus_sec := $(call as-instr,.arch_extension sec,+sec)
AFLAGS_sysfs_v7.o :=-Wa,-march=armv7-a$(plus_sec)
... but it's not being picked up.
With V=1 I can not see what's passed to the assembler, only the compiler.
Regards,
Robert
..."What I look forward to is continued immaturity followed by death." -
Dave Barry
My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
next prev parent reply other threads:[~2011-05-09 20:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 6:28 Third party toolchain, kernel, bootloader Robert Berger
2011-05-06 17:09 ` Darren Hart
2011-05-07 19:42 ` Robert Berger
2011-05-07 22:10 ` Xianghua Xiao
2011-05-08 15:29 ` Robert Berger
2011-05-09 17:39 ` Robert Berger
2011-05-09 17:57 ` Koen Kooi
2011-05-09 20:21 ` Robert Berger [this message]
2011-05-09 21:18 ` Darren Hart
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='iq9icp$d63$1@dough.gmane.org' \
--to=gmane@reliableembeddedsystems.com \
--cc=poky@pokylinux.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 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.