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]

Message-ID: <aa34ef71-d341-6660-27c1-c94ece65879b@ti.com>
Date:   Tue, 18 Apr 2017 15:42:41 +0530
From:   Sekhar Nori <nsekhar@...com>
To:     Jonathan Cameron <jic23@...nel.org>,
        Randy Dunlap <rdunlap@...radead.org>
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

Hi Jonathan, Randy,

On Friday 14 April 2017 08:53 PM, Jonathan Cameron wrote:
> On 14/04/17 16:23, Randy Dunlap wrote:
>> 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.
>>
> Agreed!

Alright, I will try to come up with something more generic and post
another version.

Thanks,
Sekhar