From: Kumar Gala <kumar.gala@freescale.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Tom Rini <trini@kernel.crashing.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linuxppc-embedded list <linuxppc-embedded@ozlabs.org>
Subject: PPC uImage build not reporting correctly
Date: Fri, 6 May 2005 10:23:05 -0500 [thread overview]
Message-ID: <cbf07e669ed84066a0bc366ca254123b@freescale.com> (raw)
Sam,
Tom pointed me at you to look at a makefile issue with
arch/ppc/boot/images/Makefile. When I do the following:
$ make uImage
CHK include/linux/version.h
make[1]: `arch/ppc/kernel/asm-offsets.s' is up to date.
CHK include/linux/compile.h
CHK usr/initramfs_list
UIMAGE arch/ppc/boot/images/uImage
Image Name: Linux-2.6.12-rc3
Created: Fri May 6 10:19:28 2005
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 993322 Bytes = 970.04 kB = 0.95 MB
Load Address: 0x00000000
Entry Point: 0x00000000
Image: arch/ppc/boot/images/uImage not made
The issue is that the file arch/ppc/boot/images/uImage does exit (the
'not made' is not correct).
$(obj)/uImage: $(obj)/vmlinux.gz
$(Q)rm -f $@
$(call if_changed,uimage)
@echo ' Image: $@' $(if $(wildcard $@),'is ready','not made')
It seems the $(wildcard $@) expands at the start of the rule. Any
ideas?
- kumar
next reply other threads:[~2005-05-06 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 15:23 Kumar Gala [this message]
2005-05-06 21:45 ` PPC uImage build not reporting correctly Sam Ravnborg
2005-05-06 21:57 ` Kumar Gala
[not found] <Pine.LNX.4.63.0505061718380.6288@xmission.xmission.com>
2005-05-09 15:19 ` Kumar Gala
2005-05-10 4:28 ` Sam Ravnborg
2005-05-10 10:34 ` cpclark
2005-05-11 5:01 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2005-05-10 15:14 Stephen Warren
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=cbf07e669ed84066a0bc366ca254123b@freescale.com \
--to=kumar.gala@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sam@ravnborg.org \
--cc=trini@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).