From: Russell King <rmk@arm.linux.org.uk>
To: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Michal Marek <mmarek@suse.cz>
Subject: lzma targets always get rebuilt
Date: Sun, 4 Nov 2012 13:34:13 +0000 [thread overview]
Message-ID: <20121104133412.GA19301@flint.arm.linux.org.uk> (raw)
$ emake -j2 O=../build/omap4/ uImage V=2
...
CHK include/generated/compile.h
echo ' Kernel: arch/arm/boot/Image is ready'
Kernel: arch/arm/boot/Image is ready
LZMA arch/arm/boot/compressed/piggy.lzma - due to command line change
AS arch/arm/boot/compressed/piggy.lzma.o - due to: arch/arm/boot/compressed/piggy.lzma
LD arch/arm/boot/compressed/vmlinux - due to: arch/arm/boot/compressed/piggy.lzma.o
OBJCOPY arch/arm/boot/zImage - due to: arch/arm/boot/compressed/vmlinux
echo ' Kernel: arch/arm/boot/zImage is ready'
Kernel: arch/arm/boot/zImage is ready
UIMAGE arch/arm/boot/uImage - due to: arch/arm/boot/zImage
Image Name: Linux-3.7.0-rc3+
Created: Sun Nov 4 13:31:13 2012
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1756112 Bytes = 1714.95 kB = 1.67 MB
Load Address: 0x80008000
Entry Point: 0x80008000
echo ' Image arch/arm/boot/uImage is ready'
Image arch/arm/boot/uImage is ready
This happens every time - Kbuild always thinks that the LZMA command has
changed. Here's the .cmd file for this:
cmd_arch/arm/boot/compressed/piggy.lzma := (cat arch/arm/boot/compressed/../Image | lzma -9 && printf \\\\200\\\\111\\\\113\\\\000) > arch/arm/boot/compressed/piggy.lzma || (rm -f arch/arm/boot/compressed/piggy.lzma ; false)
I suspect it's those multiple \ which are causing problems...
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
reply other threads:[~2012-11-04 13:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121104133412.GA19301@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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
all inboxes | Powered by JetHome®