From: Randy Dunlap <randy.dunlap@oracle.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Oleg Verych <olecom@flower.upol.cz>,
kbuild devel <kbuild-devel@lists.sourceforge.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC/RFT] kbuild: save ARCH & CROSS_COMPILE
Date: Mon, 8 Oct 2007 21:53:16 -0700 [thread overview]
Message-ID: <20071008215316.6e186b89.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20071009041743.GA21552@uranus.ravnborg.org>
On Tue, 9 Oct 2007 06:17:43 +0200 Sam Ravnborg wrote:
> >
> > What about, that this is the first ever prompt, that must be shown and
> > written to the .config?
> Two issues to fix before we can do this:
> 1) chocie values cannot have more than one prompt
> 2) We need to share much more Kconfig* between the individual architectures
> First step is to let all arch's use drivers/Kconfig
2) isn't terribly difficult, just takes some time and willingness
of $arch maintainers to some changes, but please explain a bit more
why it is needed...?
> Let's get the two items above solved then we can revisit adding arch selection
> to kconfig (where it belongs in the end).
> And neither require a rewrite of kconfig...
>
> > Also, i'd like to propose sequencing of config-enable-build-this-unit
> > in config file(s), thus Makefile(s) (sometimes very small and stupid)
> > will be not necessary. Additional link ordering can be supplied as
> > meta-config information there. Shell scripting, very ugly in the view
> > of make syntax, will be natural in config files. Extending build
> > process to get hidden dependencies or right linking/other magic is
> > part of particular configuration. Hm?
> Discussed before but so far no patches has shown up.
---
~Randy
next prev parent reply other threads:[~2007-10-09 4:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 20:02 Sam Ravnborg
2007-10-08 20:50 ` Oleg Verych
2007-10-09 4:17 ` Sam Ravnborg
2007-10-09 4:53 ` Randy Dunlap [this message]
2007-10-09 5:28 ` Randy Dunlap
2007-10-09 6:01 ` Sam Ravnborg
2007-10-09 8:37 ` Oleg Verych
2007-10-08 21:12 ` Adrian Bunk
2007-10-08 21:20 ` Giacomo Catenazzi
2007-10-09 6:03 ` Sam Ravnborg
2007-10-09 9:54 ` Adrian Bunk
2007-10-09 9:39 ` Andi Kleen
2007-10-09 10:00 ` Sam Ravnborg
2007-10-09 11:08 ` Andi Kleen
2007-10-09 14:09 ` Jeff Dike
2007-10-09 16:34 ` Sam Ravnborg
2007-10-09 17:44 ` Jeff Dike
2007-10-10 2:35 ` Kristoffer Ericson
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=20071008215316.6e186b89.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=olecom@flower.upol.cz \
--cc=sam@ravnborg.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
Powered by JetHome