linux-kernel - Re: [PATCH] tools: iio: add ability to pass kernel headers

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, 14 Apr 2017 08:23:03 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Jonathan Cameron <jic23@...nel.org>, Sekhar Nori <nsekhar@...com>
Cc:     Hartmut Knaack <knaack.h@....de>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Peter Meerwald-Stadler <pmeerw@...erw.net>,
        linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tools: iio: add ability to pass kernel headers

On 04/14/17 07:42, Jonathan Cameron wrote:
> On 11/04/17 12:06, Sekhar Nori wrote:
>> Very often, especially when cross compiling, there is a need
>> to pass kernel headers different from those installed on the
>> build machine.
>>
>> Add support for doing this for iio utils by using the
>> 'INSTALL_HDR_PATH' environment variable. This is supported by
>> 'make headers_install' for installing kernel headers at a
>> user specified location. So you will do:
>>
>> $ make headers_install ARCH=arm INSTALL_HDR_PATH=<absolute-path>
>> $ make -C tools/iio ARCH=arm INSTALL_HDR_PATH=<absolute-path>
>>
>> Signed-off-by: Sekhar Nori <nsekhar@...com>
> 
> It's a bit of an oddity as that usually refers to where to put
> the headers rather than where they are.
> 
> Is there a more general solution?  I couldn't find anything
> particularly consistent in tools.

Whatever the solution is, it should be used for all tools/, not just iio.

>> ---
>>  tools/iio/Makefile | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)


-- 
~Randy