From: Arjan van de Ven <arjanv@redhat.com>
To: "Heater, Daniel (IndSys, " "GEFanuc, VMIC)" <Daniel.Heater@gefanuc.com>
Cc: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: Re: Distributing drivers independent of the kernel source tree
Date: 26 Sep 2002 23:08:39 +0200 [thread overview]
Message-ID: <1033074519.2698.5.camel@localhost.localdomain> (raw)
In-Reply-To: <A9713061F01AD411B0F700D0B746CA6802FC14D6@vacho6misge.cho.ge.com>
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]
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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-09-26 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 20:55 Distributing drivers independent of the kernel source tree Heater, Daniel (IndSys, GEFanuc, VMIC)
2002-09-26 21:08 ` Arjan van de Ven [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2002-09-26 21:16 Heater, Daniel (IndSys, GEFanuc, VMIC)
2002-09-27 7:35 ` Arjan van de Ven
2002-09-26 21:55 Heater, Daniel (IndSys, GEFanuc, VMIC)
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=1033074519.2698.5.camel@localhost.localdomain \
--to=arjanv@redhat.com \
--cc=Daniel.Heater@gefanuc.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 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.