From: Matthew McClintock <msm@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Missing oftree_dtb and and oftree_dtb_len breaking compile
Date: Mon, 28 Aug 2006 13:34:33 -0500 [thread overview]
Message-ID: <1156790073.5083.3.camel@localhost> (raw)
In-Reply-To: <20060825231228.136b76c5@localhost.localdomain>
On Fri, 2006-08-25 at 23:12 +0100, Bryan O'Donoghue wrote:
> Hmm, I added, the following options to my config file.
>
> <snip>
> /* pass open firmware flat tree */
> #define CONFIG_OF_FLAT_TREE 1
>
> /* maximum size of the flat tree (8K) */
> #define OF_FLAT_TREE_MAX_SIZE 8192
>
> #define OF_CPU "PowerPC,MPC875"
> #define OF_TBCLK (CFG_8xx_CPUCLK_MAX / 16)
> #define CONFIG_OF_HAS_BD_T 1
> #define CONFIG_OF_HAS_UBOOT_ENV 1
> <snip>
>
> make generates an error for oftree_dtb since it and oftree_dtb_len don't seem
> to be defined _at_all_ anywhere in U-Boot aside from four extern declarations.
Could you possibly show us the specific compile error? The correct fix
would be, if you do not have CONFIG_OF_FLAT_TREE defined then the code
that hits those variables should not be compiled.
-Matthew
prev parent reply other threads:[~2006-08-28 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 22:12 [U-Boot-Users] Missing oftree_dtb and and oftree_dtb_len breaking compile Bryan O'Donoghue
2006-08-28 18:34 ` Matthew McClintock [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=1156790073.5083.3.camel@localhost \
--to=msm@freescale.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