From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] GCC-4.3.3 in toolchain fails to compile
Date: Thu, 28 May 2009 10:26:47 +0200 [thread overview]
Message-ID: <8763fl8wfs.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <56ea0bb80905272314k37d90aaep7af8de9aa846b1f9@mail.gmail.com> (Paul Archer's message of "Thu\, 28 May 2009 16\:14\:48 +1000")
>>>>> "Paul" == Paul Archer <ptarcher@gmail.com> writes:
Hi,
Paul> Hey Peter,
Paul> Thanks for the reply
Paul> Making this change let me build the toolchain, and by using the
Paul> snapshot-20090522 I was able to build and boot. Thank you for the
Paul> change.
Paul> With regards to u-boot, I have u-boot working brilliantly with
Paul> u-boot-2009.06-rc1, however I was having trouble with the u-boot tools
Paul> for reading the enviroment from linux. I had trouble building this run
Paul> on the target, I constantly got can't find file
Paul> '/usr/bin/fw_printenv', but thats another story.
I've fixed the issue with building the target-tools with 2009.06-rc1+
in my tree at work, but I haven't pushed it upstream yet as we haven't
any 2009.06-rcX support in BR (and I won't add it so close to the
release). I'll check it in next week after the release.
If you need it earlier, you could try to apply the following yourself:
commit aa8564860f13b4f295861e256a3955f57c6b23df
Author: peko <peko@a61a55d3-c7e0-402d-9e56-82086cc33c8d>
Date: Tue May 5 16:01:30 2009 +0000
u-boot: target tools: use library files from their original location
u-boot 2009.06-rc1 has changed the tools/ logic, and no longer adds
symbolic links to the needed library files in the tools directory.
Fix build by referencing the library files in their original
location.
diff --git a/target/u-boot/Makefile.in b/target/u-boot/Makefile.in
index 6f1a83e..85fac6c 100644
--- a/target/u-boot/Makefile.in
+++ b/target/u-boot/Makefile.in
@@ -196,16 +196,19 @@ $(U_BOOT_TOOLS): $(U_BOOT_DIR)/$(U_BOOT_BIN)
$(TARGET_DIR)/usr/bin/mkimage: $(U_BOOT_DIR)/$(U_BOOT_BIN)
mkdir -p $(@D)
- $(TARGET_CC) -I$(U_BOOT_DIR)/include -DUSE_HOSTCC -o $@ \
- $(U_BOOT_DIR)/tools/mkimage.c \
- $(addprefix $(U_BOOT_DIR)/tools/,crc32.c image.c md5.c sha1.c fdt*
+ $(TARGET_CC) -I$(U_BOOT_DIR)/include -I$(U_BOOT_DIR)/tools \
+ -DUSE_HOSTCC -o $@ \
+ $(U_BOOT_DIR)/tools/mkimage.c $(U_BOOT_DIR)/common/image.c \
+ $(addprefix $(U_BOOT_DIR)/lib_generic/,crc32.c md5.c sha1.c) \
+ $(U_BOOT_DIR)/libfdt/fdt*.c
+
$(STRIPCMD) $(STRIP_STRIP_UNNEEDED) $@
$(TARGET_DIR)/usr/sbin/fw_printenv: $(U_BOOT_DIR)/$(U_BOOT_BIN)
mkdir -p $(@D)
$(TARGET_CC) -I$(U_BOOT_DIR)/include -I$(LINUX_HEADERS_DIR)/include \
-DUSE_HOSTCC -o $@ \
- $(U_BOOT_DIR)/tools/env/*.c $(U_BOOT_DIR)/tools/crc32.c
+ $(U_BOOT_DIR)/tools/env/*.c $(U_BOOT_DIR)/lib_generic/crc32.c
$(STRIPCMD) $(STRIP_STRIP_UNNEEDED) $@
ln -sf fw_printenv $(TARGET_DIR)/usr/sbin/fw_setenv
Paul> Thanks for your help peter.
You're welcome.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-05-28 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 3:32 [Buildroot] GCC-4.3.3 in toolchain fails to compile Paul Archer
2009-05-24 19:37 ` Peter Korsgaard
2009-05-28 6:14 ` Paul Archer
2009-05-28 8:26 ` Peter Korsgaard [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=8763fl8wfs.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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