From: M. Warner Losh <imp@bsdimp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] latest (1.3.1) doesn't compile: files missing
Date: Sat, 19 Jan 2008 20:48:23 -0700 (MST) [thread overview]
Message-ID: <20080119.204823.387223958.imp@bsdimp.com> (raw)
In-Reply-To: <20080120010721.EA1B424764@gemini.denx.de>
In message: <20080120010721.EA1B424764@gemini.denx.de>
Wolfgang Denk <wd@denx.de> writes:
: In message <20080118.185100.1159141701.imp@bsdimp.com> you wrote:
: > There are two missing files from the distribution that prevents uboot
: > from compiling.
:
: What sort of toolchain are you using?
binutils 2.15 and gcc 4.2.1. The problem turned out to be the
combination: gcc 4.2.1 produced code that binutils couldn't assemble
properly. That was what was causing the relocation error.
: > stddef.h is included by a few different things, but can be a blank
: > file.
: >
: > stdarg.h is included by a couple of things, and can be a trivial
: > implementation (attached).
: >
: > These are both host includes, and likely shouldn't be included at all
: > in the boot loader code proper.
: >
: > This is when building the MPC8548CDS config.
: >
: > I also get link errors on this out of the box:
:
: It seems you have a toolchain issue. This is not a problem with U-Boot
: code.
The two include files aren't a toolchain issue. They can't be because
uboot's makefile has said not to include anything from the standard
include files. These files aren't included with u-boot.
Warner
next prev parent reply other threads:[~2008-01-20 3:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 1:51 [U-Boot-Users] latest (1.3.1) doesn't compile: files missing M. Warner Losh
2008-01-20 1:07 ` Wolfgang Denk
2008-01-20 3:48 ` M. Warner Losh [this message]
2008-01-20 9:49 ` Wolfgang Denk
2008-01-20 9:42 ` Wolfgang Denk
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=20080119.204823.387223958.imp@bsdimp.com \
--to=imp@bsdimp.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