From: Jeff Dike <jdike@karaya.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: UML kbuild patch
Date: Mon, 23 Sep 2002 21:34:20 -0500 [thread overview]
Message-ID: <200209240234.VAA06026@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Mon, 23 Sep 2002 19:24:01 EST." <Pine.LNX.4.44.0209231913060.13892-100000@chaos.physics.uiowa.edu>
kai@tp1.ruhr-uni-bochum.de said:
> The actual executable UML generates is called "linux" anyway, so its
> Makefile can have its own rule (as for other archs the boot images)
> which builds "linux" from "vmlinux" using gcc and the link script. -
> I.e. the same way as UML used to do it earlier, anyway.
I'd actually prefer the one-stage link. That takes better advantage of
the infrastructure that you've put in place.
Instead of making LDFLAGS_vmlinux available to the arch Makefile, can
you make cmd_link_vmlinux available? Then I can just rewrite it.
That looks like it has no impact on the global Makefile except for moving
it above the include of the arch Makefile.
Jeff
next prev parent reply other threads:[~2002-09-24 1:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 1:09 UML kbuild patch Jeff Dike
2002-09-24 0:24 ` Kai Germaschewski
2002-09-24 2:34 ` Jeff Dike [this message]
2002-09-24 12:16 ` Oleg Drokin
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=200209240234.VAA06026@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@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.