mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chaitanya Hazarey <c.v.hazarey@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Why dependance of linux kernel on linux-kernel-headers package ?
Date: Fri, 28 Oct 2005 12:39:48 +0530	[thread overview]
Message-ID: <9a9abfb40510280009v3f340f9dve02d6ffa110ae856@mail.gmail.com> (raw)

Hi all,

I would like to know about some things regarding the current scheme of
things in the linux kernel compilation procedure on Debian machines.

Its a bicth  is that if I have to compile  specific modules against a
specific kernel version ( against  header files from that specific
version ).

The problem being that because of the kernel-headers package, the gcc
(in kernel make procedure) will pick up the kernel headers from the
package specific directories but not from the /usr/src/linux path
where my specific files reside.

The work-around though simple that to change the -I in the gcc path is
not simple as the frame-work is like very rigid about the headers path
in the linux kernel.


How do I make my kernel to take the kernel headers from an alternate
location. There should have been an alternate way to specify at a
single location the alternate configuration of the header file
location. But this does not seem to be the case.


Thanks,

Warm Regards,

Chaitanya V. Hazarey


ps:

Description of the linux-kernel-headers package

"Linux Kernel Headers for development

This package provides headers from the Linux kernel.  These headers
are used by the installed headers for GNU glibc and other system libraries."

             reply	other threads:[~2005-10-28  7:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28  7:09 Chaitanya Hazarey [this message]
2005-10-28  7:18 ` Mark Nipper

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=9a9abfb40510280009v3f340f9dve02d6ffa110ae856@mail.gmail.com \
    --to=c.v.hazarey@gmail.com \
    --cc=linux-kernel@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 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®