From: Lewis Zhou <lewisou@gmail.com>
To: barebox@lists.infradead.org
Subject: selected processor does not support `rev r7,r7'
Date: Wed, 20 Mar 2019 12:57:07 +0800 [thread overview]
Message-ID: <CAD_Pvub19JJgwwkZrNX7iz47f-jib5hiUgE+8Z=2cSf80=YygQ@mail.gmail.com> (raw)
Hi
I got a compiling error, please see the log below:
lewis@lewis-ubuntu:~/OpenProj/barebox$ make ARCH=arm
CROSS_COMPILE=arm-cortex_a8-linux-gnueabihf- am335x_mlo_defconfig
#
# configuration written to .config
#
lewis@lewis-ubuntu:~/OpenProj/barebox$ make ARCH=arm
CROSS_COMPILE=arm-corte-linux-gnueabihf-
Generating include/generated/mach-types.h
CHK include/generated/version.h
CHK include/generated/utsrelease.h
CREATE include/config.h
HOSTCC scripts/basic/fixdep
CC arch/arm/lib/asm-offsets.s
GEN include/generated/asm-offsets.h
HOSTCC scripts/dtc/dtc.o
HOSTCC scripts/dtc/flattree.o
HOSTCC scripts/dtc/fstree.o
HOSTCC scripts/dtc/data.o
HOSTCC scripts/dtc/livetree.o
HOSTCC scripts/dtc/treesource.o
HOSTCC scripts/dtc/srcpos.o
HOSTCC scripts/dtc/checks.o
HOSTCC scripts/dtc/util.o
HOSTCC scripts/dtc/dtc-lexer.lex.o
HOSTCC scripts/dtc/dtc-parser.tab.o
HOSTLD scripts/dtc/dtc
HOSTCC scripts/dtc/fdtget.o
HOSTCC scripts/dtc/fdt.o
HOSTCC scripts/dtc/fdt_ro.o
HOSTCC scripts/dtc/fdt_strerror.o
HOSTCC scripts/dtc/fdt_wip.o
HOSTCC scripts/dtc/fdt_overlay.o
HOSTCC scripts/dtc/fdt_empty_tree.o
HOSTCC scripts/dtc/fdt_rw.o
HOSTCC scripts/dtc/fdt_sw.o
HOSTLD scripts/dtc/fdtget
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
HOSTCC scripts/mod/modpost.o
HOSTCC scripts/mod/sumversion.o
HOSTLD scripts/mod/modpost
HOSTCC scripts/bin2c
HOSTCC scripts/mkimage
HOSTCC scripts/fix_size
HOSTCC scripts/bareboxenv
HOSTCC scripts/bareboxcrc32
HOSTCC scripts/kernel-install
HOSTCC scripts/omap_signGP
HOSTCC scripts/mk-omap-image
CC common/memory.o
{standard input}: Assembler messages:
{standard input}:123: Error: selected processor does not support `rev
r7,r7' in Thumb mode
{standard input}:135: Error: selected processor does not support `rev
r7,r7' in Thumb mode
scripts/Makefile.build:249: recipe for target 'common/memory.o' failed
make[1]: *** [common/memory.o] Error 1
Makefile:785: recipe for target 'common' failed
make: *** [common] Error 2
lewis@lewis-ubuntu:~/OpenProj/barebox$
Kind regards,
Lewis
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2019-03-20 4:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 4:57 Lewis Zhou [this message]
2019-03-20 7:52 ` Sascha Hauer
2019-03-21 1:03 ` Lewis Zhou
2019-03-21 7:33 ` Sascha Hauer
2019-03-21 7:53 ` Lewis Zhou
2019-03-21 8:06 ` Sascha Hauer
[not found] ` <CAD_PvuY8oVy3Ny65bcF2a3LPC0R4+8uXCu6qda6CcbY+Ji+3JQ@mail.gmail.com>
[not found] ` <CAPWKHJSLmc1+-rV0rZeGn37uhkWwKsqmWXZSGJAs32zLE=Hxtg@mail.gmail.com>
2019-03-21 8:49 ` Lewis Zhou
2019-03-21 9:25 ` Juergen Borleis
2019-03-22 1:02 ` Lewis Zhou
2019-03-22 8:07 ` STM32MP1 SoC support in latest Barebox gianluca
2019-03-22 9:31 ` gianluca
2019-12-25 8:32 ` Ahmad Fatoum
2019-03-22 9:46 ` Yann Sionneau
2019-03-22 11:24 ` Robert Schwebel
2019-03-22 1:22 ` selected processor does not support `rev r7,r7' Lewis Zhou
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='CAD_Pvub19JJgwwkZrNX7iz47f-jib5hiUgE+8Z=2cSf80=YygQ@mail.gmail.com' \
--to=lewisou@gmail.com \
--cc=barebox@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