kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: alexei@alexeicolin.com (Alexei Colin)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Why can not install kernel headers?
Date: Sun, 23 Dec 2012 15:53:55 -0500	[thread overview]
Message-ID: <50D76F63.9050906@alexeicolin.com> (raw)
In-Reply-To: <201212240101374847025@gmail.com>

On 12/23/2012 12:01 PM, mobile.parmenides wrote:
> 
> I am reading an article about kernel header installtion, its links as follows: 
> http://lxr.linux.no/#linux+v2.6.32/Documentation/make/headers_install.txt#L11
> 
> Following a command given by the article:
> 		make headers_install ARCH=i386 INSTALL_HDR_PATH=/usr/include
> the kernel headers should be installed into '/usr/include'. However, when checking 
> '/usr/include/linux' and '/usr/include/asm', I found actually these kernel headers have
> not installed (by checking timestamps). 
> 
> In fact, kernel headers have be installed into 'include' subdirectory of kernel top-level 
> directory. Obviously,  the 'INSTALL_HDR_PATH' parameter in the above command 
> does not take effect. Is there any way to deal with the problem? If I have to use 'cp' to
> install headers by hand, the 'INSTALL_HDR_PATH' seems not to play its roles.
The following contradicts the examples in
Documentation/make/headers_install.txt, but in my case (android tree),
the make command creates an 'include' subdirectory in $INSTALL_HDR_PATH.
That is, if I do
make INSTALL_HDR_PATH=/path/to/headers/ headers_install
Then, the headers are installed into /path/to/headers/include.

      reply	other threads:[~2012-12-23 20:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-23 17:01 Why can not install kernel headers? mobile.parmenides
2012-12-23 20:53 ` Alexei Colin [this message]

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=50D76F63.9050906@alexeicolin.com \
    --to=alexei@alexeicolin.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).