From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] mx51evk build failure
Date: Tue, 19 Oct 2010 13:07:21 +0200 [thread overview]
Message-ID: <4CBD7BE9.5030102@denx.de> (raw)
In-Reply-To: <20101019105015.GA5729@bee.dooz.org>
On 10/19/2010 12:50 PM, Lo?c Minier wrote:
> Hey there
>
> I'm following the u-boot list and see that some mx5 changes are being
> pushed regularly to u-boot.git master, but the board doesn't build for
> me (make CROSS_COMPILE=arm-linux-gnueabi- mrproper mx51evk_config +
> make CROSS_COMPILE=arm-linux-gnueabi- all), it fails with board.c:459:
> error: ?CONFIG_SYS_SDRAM_BASE? undeclared; I guess this is because the
> board needs porting to the relocation changes?
Yes. I have at least a patch that fix the compiling issues and I could
test on a 2.5 board. However, it sets still
CONFIG_SYS_ARM_WITHOUT_RELOC. Hoever, it is ugly that the board does not
compile, and I weill send in anyway the patch to the ML.
>
> I just wonder how the various patches related to mx5 get built; do you
> revert the relocation changes locally as a workaround before build?
No. There is a second MX5 board in mainline, that I used for testing.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
parent reply other threads:[~2010-10-19 11:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20101019105015.GA5729@bee.dooz.org>]
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=4CBD7BE9.5030102@denx.de \
--to=sbabic@denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.