From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] u-boot compiler issue
Date: Tue, 17 May 2011 09:01:30 +0200 [thread overview]
Message-ID: <20110517090130.7aae0ca7@surf> (raw)
In-Reply-To: <4DCBEC13.2050802@visionsystems.de>
Hello,
On Thu, 12 May 2011 16:17:55 +0200
Yegor Yefremov <yegor_sub1@visionsystems.de> wrote:
> I was building u-boot with buildroots created toolchain. Everything was working except
> that pointer passed via r8 was not writable (RAM was not configured
> etc.).
Could you give more details about this analysis ?
> But if the same code was compiled with CodeSourcery everything
> was working. Here gcc configuration from buidroot:
Does the U-Boot compilation fails, or the compilation works but U-Boot
fails to run on the device ? If it's the latter, then which version of
U-Boot are you using ? Only recent versions of U-Boot work well with
gcc 4.5.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-05-17 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 14:17 [Buildroot] u-boot compiler issue Yegor Yefremov
2011-05-17 7:01 ` Thomas Petazzoni [this message]
2011-05-17 8:15 ` Yegor Yefremov
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=20110517090130.7aae0ca7@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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