From: Cam <camilo@mesias.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Error on making u-boot
Date: Sun, 14 Dec 2003 11:43:01 +0000 [thread overview]
Message-ID: <3FDC4CC5.4000501@mesias.co.uk> (raw)
In-Reply-To: <20031214023804.61973.qmail@web15007.mail.bjs.yahoo.com>
SAM SONG
> Have you met it?After masking three files,hello_world.bin,sched.bin
> ,timer.bin in Makefile of examples directory,it succeeded.But there
> aren't three files in the directory.I use Montavista Linux Pro 3.0.Any
> hints?
There was recently a patch which works around a bug in the montavista
objcopy. The problem is that it doesn't handle SREC input (even if you
use -I srec).
The workaround is to ignore the problem - like you say the make will
succeed eventually, or change the commands in the examples/Makefile like
this:
Near the rule that says:
%.bin: %.srec
Replace this line:
$(OBJCOPY) -O binary $< $@ 2>/dev/null
With this line:
$(OBJCOPY) -O binary $(<:.srec=) $@ 2>/dev/null
-Cam
prev parent reply other threads:[~2003-12-14 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-14 2:38 [U-Boot-Users] Error on making u-boot SAM SONG
2003-12-14 11:43 ` Cam [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=3FDC4CC5.4000501@mesias.co.uk \
--to=camilo@mesias.co.uk \
--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