mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: Jonathan Cameron <jic23@kernel.org>,
	Randy Dunlap <rdunlap@infradead.org>
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: Tue, 18 Apr 2017 15:42:41 +0530	[thread overview]
Message-ID: <aa34ef71-d341-6660-27c1-c94ece65879b@ti.com> (raw)
In-Reply-To: <aa079d7f-3769-6961-1a13-8448ad0bc5cf@kernel.org>

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@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.
>>
> Agreed!

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

Thanks,
Sekhar

  reply	other threads:[~2017-04-18 10:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 11:06 Sekhar Nori
2017-04-14 14:42 ` Jonathan Cameron
2017-04-14 15:23   ` Randy Dunlap
2017-04-14 15:23     ` Jonathan Cameron
2017-04-18 10:12       ` Sekhar Nori [this message]
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=aa34ef71-d341-6660-27c1-c94ece65879b@ti.com \
    --to=nsekhar@ti.com \
    --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=pmeerw@pmeerw.net \
    --cc=rdunlap@infradead.org \
    /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®