All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard H Lee <ricardohenrylee@gmail.com>
To: linux-kbuild@vger.kernel.org
Subject: Building linux headers in an non-linux environment
Date: Mon, 05 Nov 2012 22:43:36 +0000	[thread overview]
Message-ID: <50984118.2070204@gmail.com> (raw)

I'm trying to install linux headers for cygwin using crostool-ng.

ct-ng basically invokes the line:

make -C /home/richard/scratch/x86linux/.build/src/linux-3.5 
O=/home/richard/scratch/x86linux/.build/i386-unknown-linux-gnu/build/build-kernel-headers 
ARCH=x86 
INSTALL_HDR_PATH=/home/richard/x-tools/i386-unknown-linux-gnu/i386-unknown-linux-gnu/sysroot/usr 
V=1 headers_install

and it seems to have checked out v3.5 of the linux kernel.

The problem is that making the headers seems to require an existing set 
of headers already installed. The required headers seem to be in the 
include/ and arch/[target]/ directories.

What is the "correct" way to get the Makefile to use the source tree as 
the source for the linux headers?


In the top-level Makefile, I can see the following variable

 >LINUXINCLUDE    := -I$(srctree)/arch/$(hdr-arch)/include \
 >                   -Iarch/$(hdr-arch)/include/generated -Iinclude \
 >                   $(if $(KBUILD_SRC), -I$(srctree)/include) \
 >                   -include $(srctree)/include/linux/kconfig.h

but I'm not sure how to get this variable picked up. And I don't exactly 
know what to do with KBUILD_SRC.


Richard

             reply	other threads:[~2012-11-05 22:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 22:43 Richard H Lee [this message]
2012-12-09 14:35 ` Building linux headers in an non-linux environment Michal Marek
  -- strict thread matches above, loose matches on Subject: below --
2012-11-03  0:37 Richard H Lee

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=50984118.2070204@gmail.com \
    --to=ricardohenrylee@gmail.com \
    --cc=linux-kbuild@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.