LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <lists@nerdbynature.de>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: zImage.miboot and vmlinux.lds
Date: Sat, 9 Jun 2007 23:39:20 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.0.99.0706092327300.8312@foobar-g4> (raw)
In-Reply-To: <981f558c34d946fcb2683a9731f8d5ad@kernel.crashing.org>

On Sat, 9 Jun 2007, Segher Boessenkool wrote:
> vmlinux.lds should be cleaned from the main (non-arch)
> Makefile; I could swear I've sent a patch for that some
> time ago.

Well, Stephen Rothwell did (too?) and you replied to his post:
http://article.gmane.org/gmane.linux.ports.ppc.devel/5881
http://article.gmane.org/gmane.linux.ports.ppc.devel/5897

> Maybe it should be added to $(image-) unconditionally?
> Or get rid of the ifeq, preferably.

What about just adding it to clean-files, since $(image-) does not seem 
to catch it?

--- linux-2.6.22-rc3.orig/arch/powerpc/boot/Makefile	2007-05-26 04:55:14.000000000 +0200
+++ linux-2.6.22-rc3/arch/powerpc/boot/Makefile	2007-06-09 23:38:07.000000000 +0200
@@ -81,7 +81,7 @@ $(obj)/zImage.lds $(obj)/zImage.coff.lds
  	@cp $< $@

  clean-files := $(zlib) $(zlibheader) $(zliblinuxheader) \
-		empty.c zImage.coff.lds zImage.lds
+		empty.c zImage.coff.lds zImage.lds zImage.miboot

  quiet_cmd_bootcc = BOOTCC  $@
        cmd_bootcc = $(CROSS32CC) -Wp,-MD,$(depfile) $(BOOTCFLAGS) -c -o $@ $<


-- 
make bzImage, not war

  reply	other threads:[~2007-06-09 21:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-28 19:32 zImage.miboot and vmlinux.lds Christian Kujau
2007-06-09 19:14 ` Christian Kujau
2007-06-09 21:03   ` Segher Boessenkool
2007-06-09 21:39     ` Christian Kujau [this message]
2007-06-11  0:25       ` Stephen Rothwell

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=alpine.DEB.0.99.0706092327300.8312@foobar-g4 \
    --to=lists@nerdbynature.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=segher@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