public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Roland McGrath <roland@redhat.com>
Cc: Pavel Machek <pavel@ucw.cz>,
	akpm@linux-foundation.org, linux-kbuild@vger.kernel.org
Subject: Re: [patch 11/18] kconfig CROSS_COMPILE option
Date: Sat, 19 Sep 2009 15:13:16 +0200	[thread overview]
Message-ID: <20090919131316.GA26044@merkur.ravnborg.org> (raw)
In-Reply-To: <20090919121950.A599F2728@magilla.sf.frob.com>

On Sat, Sep 19, 2009 at 05:19:50AM -0700, Roland McGrath wrote:
> 
> One thing I'd thought to do in "finishing it up" was to write just the
> $ARCH string alone to kernel.arch (then needing a kernel.subarch too)
> rather than a makefile fragment.  My thinking is that any scripty things
> that would like to look at a given build dir (as in the installed
> /lib/modules/foo/build in kernel-devel packages) would like to extract
> the arch name as well as the kernel release string, and not necessarily
> do it by running make or parsing makeish assignment lines.

Another approach would be to ask kbuild for
this information so we do not expose various filenames to the
outer world.

Somthing like this:

diff --git a/Makefile b/Makefile
index c41035a..8f488c9 100644
--- a/Makefile
+++ b/Makefile
@@ -1528,6 +1523,12 @@ kernelrelease:
 kernelversion:
 	@echo $(KERNELVERSION)
 
+kernelarch:
+	@echo $(ARCH)
+
+kernelsubarch:
+	@echo $(SUBARCH)
+
 # Single targets
 # ---------------------------------------------------------------------------
 # Single targets are compatible with:

This is analogous to the way we ask for
kernelrelease and kernelversion these days.

	Sam

  reply	other threads:[~2009-09-19 13:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18 19:49 [patch 11/18] kconfig CROSS_COMPILE option akpm
2009-09-19  9:02 ` Sam Ravnborg
2009-09-19 12:19   ` Roland McGrath
2009-09-19 13:13     ` Sam Ravnborg [this message]
2009-09-19 23:48       ` Roland McGrath
2009-09-20 10:31         ` Sam Ravnborg
2009-09-21  3:53           ` Roland McGrath
2009-09-23  7:16           ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2009-09-14 21:49 akpm

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=20090919131316.GA26044@merkur.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=roland@redhat.com \
    /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