From: Reinhard Meyer <u-boot@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Followup: GCC-4.3.5 and U-Boot (arm, reloc) not working
Date: Mon, 11 Oct 2010 11:13:23 +0200 [thread overview]
Message-ID: <4CB2D533.50103@emk-elektronik.de> (raw)
In-Reply-To: <4CB2C531.6010900@emk-elektronik.de>
Reinhard Meyer schrieb:
> Hello,
>
> I just have built gcc-4.3.5 for arm-eabi. When I compile u-boot with it,
> it stops after the DRAM: 64 MiB. I _assume_ that relocation does not work.
>
> I do not have time right now to further investigate this issue, but if
> someone else finds the same problem, this might be an issue worth
> investigating.
Followup:
Kernel compiles and works with gcc 4.3.5
Linux version 2.6.36-rc7+ (reinhard at sieb) (gcc version 4.3.5 (Buildroot 2010.11-git) ) #1 Mon Oct 11 10:37:52 CEST 2010
That _could_ indicate that the ARM u-boot relocation method is toolchain sensitive.
Reinhard
prev parent reply other threads:[~2010-10-11 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 8:05 [U-Boot] Observation: GCC-4.3.5 and U-Boot (arm, reloc) not working Reinhard Meyer
2010-10-11 9:13 ` Reinhard Meyer [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=4CB2D533.50103@emk-elektronik.de \
--to=u-boot@emk-elektronik.de \
--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