From: Andreas Schwab <schwab@suse.de>
To: jbradford@dial.pipex.com
Cc: arjanv@redhat.com (Arjan van de Ven),
Daniel.Heater@gefanuc.com, linux-kernel@vger.kernel.org,
alan@lxorguk.ukuu.org.uk, jgarzik@pobox.com
Subject: Re: Distributing drivers independent of the kernel source tree
Date: Fri, 27 Sep 2002 14:48:09 +0200 [thread overview]
Message-ID: <jed6qzy4xi.fsf@sykes.suse.de> (raw)
In-Reply-To: <200209271240.g8RCeiBH000229@darkstar.example.net> (jbradford@dial.pipex.com's message of "Fri, 27 Sep 2002 13:40:43 +0100 (BST)")
jbradford@dial.pipex.com writes:
|> > > 2. Assuming the kernel source is in /usr/src/linux is not always valid.
|> > >=20
|> > > 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.
|>
|> What about instances where there is no modular support in the kernel?
If your kernel has no module support then you cannot compile kernel
modules.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2002-09-27 12:42 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
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 [this message]
2002-09-27 13:08 ` jbradford
2002-09-30 21:35 ` Anders Gustafsson
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=jed6qzy4xi.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=Daniel.Heater@gefanuc.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=jbradford@dial.pipex.com \
--cc=jgarzik@pobox.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).