From: Vladimir Gurevich <vag@paulidav.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problems with the port to PPC 405EP ev. board
Date: Mon, 17 Mar 2003 07:23:36 -0800 [thread overview]
Message-ID: <3E75E878.2070709@paulidav.org> (raw)
In-Reply-To: 5.1.1.6.0.20030317155655.02f9aa68@dns.struinfo.it
Hello,
I'd guess that attaching your new start.S or, at least,
the diff to the original one will definitely help...
Best regards,
Vladimir
llandre wrote:
> ppc-linux-gcc -Wa,-gstabs -D__ASSEMBLY__ -g -Os -mrelocatable
> -ffixed-r14 -meabi -mrelocatable -ffixed-r14 -meabi -D__KERNEL__
> -DTEXT_BASE=0xFFF80000 -I/proj/ppc405ep/sw/u-boot/include -fno-builtin
> -pipe -DCONFIG_PPC -D__powerpc__ -DCONFIG_4xx -ffixed-r2 -ffixed-r29
> -mstring -Wa,-m405 -mcpu=405 -msoft-float -DCONFIG_PPC -D__powerpc__
> -DCONFIG_4xx -ffixed-r2 -ffixed-r29 -mstring -Wa,-m405 -mcpu=405
> -msoft-float -c -o start.o /proj/ppc405ep/sw/u-boot/cpu/ppc4xx/start.S
> /proj/ppc405ep/sw/u-boot/cpu/ppc4xx/start.S: Assembler messages:
> /proj/ppc405ep/sw/u-boot/cpu/ppc4xx/start.S:849: Error: attempt to
> .org/.space backwards? (-8)
> /proj/ppc405ep/sw/u-boot/cpu/ppc4xx/start.S:1582: Internal error!
> Assertion failure in write_contents at ../../gas/write.c line 1187.
> Please report this bug.
> make[1]: *** [start.o] Error 1
> make[1]: Leaving directory `/proj/ppc405ep/sw/u-boot/cpu/ppc4xx'
> make: *** [subdirs] Error 1
> ---------------------------------------------------------------------------
>
> I never saw an error like that. Anybody can tell me what is wrong?
next prev parent reply other threads:[~2003-03-17 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 15:11 [U-Boot-Users] Problems with the port to PPC 405EP ev. board llandre
2003-03-17 15:23 ` Vladimir Gurevich [this message]
[not found] ` <5.1.1.6.0.20030317171757.00a81480@192.168.2.1>
2003-03-17 18:25 ` Vladimir Gurevich
2003-03-18 15:49 ` llandre
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=3E75E878.2070709@paulidav.org \
--to=vag@paulidav.org \
--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