From: "Kirill A. Shutsemov" <kirill@shutemov.name>
To: Sam Ravnborg <sam@ravnborg.org>, David Woodhouse <dwmw2@infradead.org>
Cc: "Michal Marek" <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
"Américo Wang" <xiyou.wangcong@gmail.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: [PATCH, RESEND 1/2] kbuild: introduce HDR_ARCH_LIST for headers_install_all
Date: Mon, 13 Dec 2010 19:10:28 +0200 [thread overview]
Message-ID: <1292260229-10008-1-git-send-email-kirill@shutemov.name> (raw)
From: Kirill A. Shutemov <kirill@shutemov.name>
Using HDR_ARCH_LIST you can specify subset of architectures you want to get
headers for.
Signed-off-by: Kirill A. Shutemov <kirill@shutemov.name>
---
| 5 +++--
| 2 +-
2 files changed, 4 insertions(+), 3 deletions(-)
--git a/Documentation/make/headers_install.txt b/Documentation/make/headers_install.txt
index f2481ca..951eb9f 100644
--- a/Documentation/make/headers_install.txt
+++ b/Documentation/make/headers_install.txt
@@ -39,8 +39,9 @@ INSTALL_HDR_PATH indicates where to install the headers. It defaults to
The command "make headers_install_all" exports headers for all architectures
simultaneously. (This is mostly of interest to distribution maintainers,
who create an architecture-independent tarball from the resulting include
-directory.) Remember to provide the appropriate linux/asm directory via "mv"
-or "ln -s" before building a C library with headers exported this way.
+directory.) You also can use HDR_ARCH_LIST to specify list of architectures.
+Remember to provide the appropriate linux/asm directory via "mv" or "ln -s"
+before building a C library with headers exported this way.
The kernel header export infrastructure is maintained by David Woodhouse
<dwmw2@infradead.org>.
--git a/scripts/headers.sh b/scripts/headers.sh
index 1ddcdd3..978b42b 100755
--- a/scripts/headers.sh
+++ b/scripts/headers.sh
@@ -13,7 +13,7 @@ do_command()
fi
}
-archs=$(ls ${srctree}/arch)
+archs=${HDR_ARCH_LIST:-$(ls ${srctree}/arch)}
for arch in ${archs}; do
case ${arch} in
--
1.7.3.3
next reply other threads:[~2010-12-13 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 17:10 Kirill A. Shutsemov [this message]
2010-12-13 17:10 ` [PATCH, RESEND 2/2] kbuild: export linux/{a.out,kvm,kvm_para}.h on headers_install_all Kirill A. Shutsemov
2010-12-14 22:04 ` [PATCH, RESEND 1/2] kbuild: introduce HDR_ARCH_LIST for headers_install_all Michal Marek
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=1292260229-10008-1-git-send-email-kirill@shutemov.name \
--to=kirill@shutemov.name \
--cc=dwmw2@infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
--cc=xiyou.wangcong@gmail.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
all inboxes | Powered by JetHome®