From: Rafal Jaworowski <raj@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Cannot assemble cpu/ppc4xx/start.S for sequoia
Date: Thu, 21 Jun 2007 13:53:16 +0200 [thread overview]
Message-ID: <467A66AC.2070100@semihalf.com> (raw)
In-Reply-To: <467A781F.268B.006F.0@netstal.com>
Niklaus Giger wrote:
>
> After pulling the recent git merges from stefan I get the following error:
>
> ppc_4xx-gcc -D__ASSEMBLY__ -g -Os -fPIC -ffixed-r14 -meabi
> -fno-strict-aliasing -D__KERNEL__ -DTEXT_BASE=0xFFFA0000
> -I/home/ng/u-boot/build.sequoia/include2 -I/home/ng/u-boot/build.sequoia/include
> -I/home/ng/u-boot/u-boot.work/include -fno-builtin -ffreestanding -nostdinc
> -isystem /home/hcu/eldk-4.1/usr/bin/../lib/gcc/powerpc-linux/4.0.0/include -pipe
> -DCONFIG_PPC -D__powerpc__ -DCONFIG_4xx -ffixed-r2 -ffixed-r29 -mstring
> -msoft-float -Wa,-m405 -mcpu=405 -DCONFIG_440=1 -c -o
> /home/ng/u-boot/build.sequoia/cpu/ppc4xx/start.o start.S
> start.S: Assembler messages:
> start.S:1211: Error: Unrecognized opcode: `rfmci'
>
> I am using ppc_4xx-gcc --version
> ppc_4xx-gcc (GCC) 4.0.0 (DENX ELDK 4.1 4.0.0)
>
>
> Any hints would be appreciated.
>
Hi Niklaus,
Do you see any complaints about 'sed' not found? One thing that might be
going wrong is while checking for the 440 vs. 405.
The board config file is found (using sed...) to decide on the variant
-- see cpu/ppc4xx/config.mk. When the tool is not available the
config.mk would default to chosing 405 and likely lead to such problems.
kind regards,
Rafal
prev parent reply other threads:[~2007-06-21 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 11:07 [U-Boot-Users] Cannot assemble cpu/ppc4xx/start.S for sequoia Niklaus Giger
2007-06-21 11:52 ` Stefan Roese
2007-06-21 11:53 ` Rafal Jaworowski [this message]
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=467A66AC.2070100@semihalf.com \
--to=raj@semihalf.com \
--cc=u-boot@lists.denx.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