From: Nate Case <ncase@xes-inc.com>
To: Matt Sealey <matt@genesi-usa.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: Building dtc etc. for packaging
Date: Tue, 11 Nov 2008 12:00:37 -0600 [thread overview]
Message-ID: <1226426437.27415.379.camel@localhost.localdomain> (raw)
In-Reply-To: <4919C115.8040107@genesi-usa.com>
On Tue, 2008-11-11 at 11:29 -0600, Matt Sealey wrote:
> (the other tool we need is mkimage from U-Boot, I noticed Debian uses
> this
> same command name inside jigdo etc. too, sigh.. also you can't build
> the
> tools without the rest of U-Boot which is hard to envision doing just
> to
> get one command out of it - "make tools/mkimage" doesn't work and I
> got
> tired of reverse engineering the chickenscratch..)
This is a bit off-topic, but here is my ugly hack to compile a
statically linked 'mkimage' from the U-Boot tree:
Place this file, 'Makefile.mkimage' in u-boot/tools/
---[snip]---
CFLAGS = -O2 -static -I../include -DUSE_HOSTCC -I.
ASMDIR = ../include/asm
CFILES = ../lib_generic/crc32.c ../libfdt/fdt_strerror.c \
../lib_generic/sha1.c ../lib_generic/md5.c ../common/image.c \
../libfdt/fdt_wip.c ../libfdt/fdt.c ../libfdt/fdt_ro.c \
../libfdt/fdt_rw.c
mkimage: mkimage.c
mv $(ASMDIR) $(ASMDIR).back
ln -s $(ASMDIR)-i386 $(ASMDIR)
gcc $(CFLAGS) $(CFILES) mkimage.c -o mkimage
rm -f $(ASMDIR)
mv $(ASMDIR).back $(ASMDIR)
strip mkimage
default: mkimage
---[snip]---
Then just run 'make -f Makefile.mkimage' from within tools/. Of course
this uses some nasty tricks that will only work on i386 host. I don't
think I'm the first person to have this need, so others here may have
better solutions.
--
Nate Case <ncase@xes-inc.com>
next prev parent reply other threads:[~2008-11-11 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 17:29 Building dtc etc. for packaging Matt Sealey
2008-11-11 18:00 ` Nate Case [this message]
2008-11-11 20:32 ` Simon Richter
2008-11-11 22:39 ` David Gibson
2008-11-11 23:10 ` Jon Loeliger
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=1226426437.27415.379.camel@localhost.localdomain \
--to=ncase@xes-inc.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=matt@genesi-usa.com \
/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.