From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Re: [revised v2 PATCH 5/5] sparc,sparc64: unify boot/
Date: Wed, 03 Dec 2008 21:07:25 +0000 [thread overview]
Message-ID: <20081203210725.GA7255@uranus.ravnborg.org> (raw)
In-Reply-To: <20081203200044.GA6471@uranus.ravnborg.org>
On Wed, Dec 03, 2008 at 12:46:30PM -0800, David Miller wrote:
> From: Sam Ravnborg <sam@ravnborg.org>
> Date: Wed, 3 Dec 2008 21:00:44 +0100
>
> BTW:
>
> > +ifeq ($(CONFIG_SPARC64),y)
> > +quiet_cmd_piggy = PIGGY $@
> > + cmd_piggy = $(obj)/piggyback_64 $@ System.map $(ROOT_IMG)
> > +quiet_cmd_strip = STRIP $@
> > + cmd_strip = $(STRIP) -R .comment -R .note -K sun4u_init -K _end -K _start vmlinux -o $@
> > +
> > +
> > +# Actual linking
> > +$(obj)/image: vmlinux FORCE
> > + $(call if_changed,strip)
> > + @echo ' kernel: $@ is ready'
> > +
> > +$(obj)/tftpboot.img: vmlinux $(obj)/piggyback_64 System.map $(ROOT_IMG) FORCE
> > + $(call if_changed,elftoaout)
> > + $(call if_changed,piggy)
> > + @echo ' kernel: $@ is ready'
> > +
> > +$(obj)/vmlinux.aout: vmlinux FORCE
> > + $(call if_changed,elftoaout)
> > + @echo ' kernel: $@ is ready'
> > +endif
>
> This is one of the things I had to fix up when I applied these
> patches. Those linking rules need to have initial tabs not spaces
> before the commands to be run, or else the build breaks.
>
> I guess you didn't do any "make image" testing, or did you? :-)
Right - I just did "make".
>
> But don't worry I fixed that up in my tree when I applied
> these patches and I dealt with the conflict too already.
Thanks!
Sam
prev parent reply other threads:[~2008-12-03 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 20:00 [revised v2 PATCH 5/5] sparc,sparc64: unify boot/ Sam Ravnborg
2008-12-03 20:46 ` David Miller
2008-12-03 21:07 ` Sam Ravnborg [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=20081203210725.GA7255@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.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 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.