lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 5 Nov 2010 11:01:56 +0200
From:	"Kirill A. Shutemov" <kirill@...temov.name>
To:	Sam Ravnborg <sam@...nborg.org>,
	David Woodhouse <dwmw2@...radead.org>
Cc:	Michal Marek <mmarek@...e.cz>, linux-kbuild@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] kbuild: introduce ARCH_LIST for headers_install_all

Does anybody care?

On Fri, Oct 29, 2010 at 04:04:00PM +0300, Kirill A. Shutsemov wrote:
> From: Kirill A. Shutemov <kirill@...temov.name>
> 
> Using ARCH_LIST you can specify subset of architectures you want to get
> headers for.
> 
> Signed-off-by: Kirill A. Shutemov <kirill@...temov.name>
> ---
>  Documentation/make/headers_install.txt |    5 +++--
>  scripts/headers.sh                     |    2 +-
>  2 files changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/make/headers_install.txt b/Documentation/make/headers_install.txt
> index f2481ca..1abace6 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 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@...radead.org>.
> diff --git a/scripts/headers.sh b/scripts/headers.sh
> index 1ddcdd3..62bc527 100755
> --- a/scripts/headers.sh
> +++ b/scripts/headers.sh
> @@ -13,7 +13,7 @@ do_command()
>  	fi
>  }
>  
> -archs=$(ls ${srctree}/arch)
> +archs=${ARCH_LIST:-$(ls ${srctree}/arch)}
>  
>  for arch in ${archs}; do
>  	case ${arch} in
> -- 
> 1.7.3.2
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
 Kirill A. Shutemov
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ