mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lewis Zhou <lewisou@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: selected processor does not support `rev r7,r7'
Date: Thu, 21 Mar 2019 15:53:06 +0800	[thread overview]
Message-ID: <CAD_PvubAaFD=zJVrzpjq__F2Qre4XedjE8op_1GAQcf19jYOrg@mail.gmail.com> (raw)
In-Reply-To: <20190321073332.b3725avve4p6ascg@pengutronix.de>

Hi Sascha,

Here's the log:

make -f scripts/Makefile.build obj=common

arm-cortex_a8-linux-gnueabihf-gcc -Wp,-MD,common/.memory.o.d
-nostdinc -isystem
/home/lewis/x-tools/arm-cortex_a8-linux-gnueabihf/lib/gcc/arm-cortex_a8-linux-gnueabihf/8.3.0/include
-D__KERNEL__ -D__BAREBOX__ -Iinclude
-I/home/lewis/OpenProj/barebox/dts/include
-I/home/lewis/OpenProj/barebox/arch/arm/include
-I/home/lewis/OpenProj/barebox/arch/arm/include -include
/home/lewis/OpenProj/barebox/include/linux/kconfig.h -fno-builtin
-ffreestanding -D__ARM__ -fno-strict-aliasing -marm -mlittle-endian
-mabi=aapcs-linux -mno-thumb-interwork -D__LINUX_ARM_ARCH__=7
-march=armv5t -Wa,-march=armv7-a  -msoft-float -mthumb
-Wa,-mimplicit-it=always -Wa,-mno-warn-deprecated
-Iarch/arm/mach-omap/include -DTEXT_BASE=0x0 -fdata-sections
-ffunction-sections -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs
-Werror-implicit-function-declaration -fno-strict-aliasing -fno-common
-Os -pipe -mno-unaligned-access  -fno-stack-protector
-Wno-unused-but-set-variable -Wno-trampolines
-fno-delete-null-pointer-checks -Wdeclaration-after-statement
-Wno-pointer-sign    -D"KBUILD_STR(s)=#s"
-D"KBUILD_BASENAME=KBUILD_STR(memory)"
-D"KBUILD_MODNAME=KBUILD_STR(memory)" -c -o common/memory.o
common/memory.c
{standard input}: Assembler messages:
{standard input}:123: Error: selected processor does not support `rev
r7,r7' in Thumb mode

Kind regards,
Lewis

On Thu, Mar 21, 2019 at 3:33 PM Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
> On Thu, Mar 21, 2019 at 09:03:21AM +0800, Lewis Zhou wrote:
> > Hi Sascha,
> >
> > The toolchain was compiled by crosstool-NG. It used the default config
> > arm-cortex_a8-linux-gnueabi but with the hardware float enabled. So
> > the toolchain was arm-cortex_a8-linux-gnueabihf-.
>
> Could you add V=1 to your make call and post an example gcc call? one is
> enough, not the whole output.
>
> Sascha
>
>
> --
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2019-03-21  7:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20  4:57 Lewis Zhou
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 [this message]
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_PvubAaFD=zJVrzpjq__F2Qre4XedjE8op_1GAQcf19jYOrg@mail.gmail.com' \
    --to=lewisou@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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