From: Jack Mitchell <ml@communistcode.co.uk>
To: meta-ti@yoctoproject.org
Subject: u-boot compile failure
Date: Mon, 15 Oct 2012 14:32:35 +0100 [thread overview]
Message-ID: <507C1073.3060703@communistcode.co.uk> (raw)
It seems that u-boot is attempting to use GCC includes from my host
system here. This surely isn't right is it?
DEBUG: Executing shell function do_compile
NOTE: make -j 9 HOSTCC=gcc HOSTLD=ld
HOSTLDFLAGS=-L/home/jack/Projects/poky-r0005/R0005/tmp/sysroots/x86_64-linux/usr/lib
-L/home/jack/Projects/poky-r0005/R0005/tmp/sysroots/x86_64-linux/lib
-Wl,-rpath-link,/home/jack/Projects/poky-r0005/R0005/tmp/sysroots/x86_64-linux/usr/lib
-Wl,-rpath-link,/home/jack/Projects/poky-r0005/R0005/tmp/sysroots/x86_64-linux/lib
-Wl,-rpath,/home/jack/Projects/poky-r0005/R0005/tmp/sysroots/x86_64-linux/usr/lib
-Wl,-rpath,/home/jack/Projects/poky-r0005/R0005/tmp/sysroots/x86_64-linux/lib
-Wl,-O1 HOSTSTRIP=true tools
make -C tools all
make[1]: Entering directory
`/home/jack/Projects/poky-r0005/R0005/tmp/work/x86_64-linux/u-boot-mkimage-native-2011.06-r0/u-boot-2011.06/tools'
make[1]: *** No rule to make target
`/usr/lib/gcc/x86_64-unknown-linux-gnu/4.7.1/include/stddef.h', needed
by `crc32.o'. Stop.
make[1]: Leaving directory
`/home/jack/Projects/poky-r0005/R0005/tmp/work/x86_64-linux/u-boot-mkimage-native-2011.06-r0/u-boot-2011.06/tools'
make: *** [tools] Error 2
ERROR: oe_runmake failed
ERROR: Function failed: do_compile (see
/home/jack/Projects/poky-r0005/R0005/tmp/work/x86_64-linux/u-boot-mkimage-native-2011.06-r0/temp/log.do_compile.15275
for further information)
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next reply other threads:[~2012-10-15 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 13:32 Jack Mitchell [this message]
2012-10-16 1:20 ` u-boot compile failure Tom Rini
2012-10-16 8:22 ` Jack Mitchell
2012-10-16 13:00 ` Denys Dmytriyenko
2012-10-16 13:16 ` Jack Mitchell
2012-10-16 13:37 ` Denys Dmytriyenko
2012-10-16 13:54 ` Jack Mitchell
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=507C1073.3060703@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=meta-ti@yoctoproject.org \
/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.