From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Cameron <jic23@kernel.org>, Sekhar Nori <nsekhar@ti.com>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools: iio: add ability to pass kernel headers
Date: Fri, 14 Apr 2017 08:23:03 -0700 [thread overview]
Message-ID: <6104d595-462b-c154-5b6a-73ed33d0b258@infradead.org> (raw)
In-Reply-To: <1f009aa7-f1c0-cf7b-344b-fe83f3b4b7b9@kernel.org>
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@ti.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
next prev parent reply other threads:[~2017-04-14 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 11:06 [PATCH] tools: iio: add ability to pass kernel headers Sekhar Nori
2017-04-14 14:42 ` Jonathan Cameron
2017-04-14 15:23 ` Randy Dunlap [this message]
2017-04-14 15:23 ` Jonathan Cameron
2017-04-18 10:12 ` Sekhar Nori
2017-04-20 13:53 ` Sekhar Nori
2017-04-20 15:27 ` Randy Dunlap
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=6104d595-462b-c154-5b6a-73ed33d0b258@infradead.org \
--to=rdunlap@infradead.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=pmeerw@pmeerw.net \
/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;
as well as URLs for NNTP newsgroup(s).