From: "Heater, Daniel (IndSys, GEFanuc, VMIC)" <Daniel.Heater@gefanuc.com>
To: "'Arjan van de Ven'" <arjanv@redhat.com>
Cc: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: RE: Distributing drivers independent of the kernel source tree
Date: Thu, 26 Sep 2002 17:16:03 -0400 [thread overview]
Message-ID: <A9713061F01AD411B0F700D0B746CA6802FC14D7@vacho6misge.cho.ge.com> (raw)
That's true for installing modules, but I'm wondering about getting a
standalone module compiled. I.e., what is a reliable method for locating the
include files for the kernel?
I can find references on the web where this has been discussed in the past,
but I have not found a resolution.
> -----Original Message-----
> From: Arjan van de Ven [mailto:arjanv@redhat.com]
> Sent: Thursday, September 26, 2002 4:09 PM
> To: Heater, Daniel (IndSys, ""GEFanuc, VMIC)
> Cc: 'Linux Kernel Mailing List'
> Subject: Re: Distributing drivers independent of the kernel
> source tree
>
>
> On Thu, 2002-09-26 at 22:55, Heater, Daniel (IndSys, GEFanuc, VMIC)
> > 2. Assuming the kernel source is in /usr/src/linux is not
> always valid.
> >
> > 3. I currently use /usr/src/linux-`uname -r` to locate the
> kernel source
> > which is just as broken as method #2.
>
> you have to use
>
> /lib/modules/`uname -r`/build
> (yes it's a symlink usually, but that doesn't matter)
>
>
> that's what Linus decreed and that's what all distributions honor, and
> that's that make install does for manual builds.
>
> Greetings,
> Arjan van de Ven
>
next reply other threads:[~2002-09-26 21:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 21:16 Heater, Daniel (IndSys, GEFanuc, VMIC) [this message]
2002-09-27 7:35 ` Distributing drivers independent of the kernel source tree Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2002-09-26 21:55 Heater, Daniel (IndSys, GEFanuc, VMIC)
2002-09-26 20:55 Heater, Daniel (IndSys, GEFanuc, VMIC)
2002-09-26 21:08 ` Arjan van de Ven
2002-09-26 21:41 ` Alan Cox
2002-09-26 21:48 ` Jeff Garzik
2002-09-26 22:03 ` J.A. Magallon
2002-09-27 12:40 ` jbradford
2002-09-27 12:48 ` Andreas Schwab
2002-09-27 13:08 ` jbradford
2002-09-30 21:35 ` Anders Gustafsson
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=A9713061F01AD411B0F700D0B746CA6802FC14D7@vacho6misge.cho.ge.com \
--to=daniel.heater@gefanuc.com \
--cc=arjanv@redhat.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;
as well as URLs for NNTP newsgroup(s).