From: Peter Samuelson <peter@cadcamlab.org>
To: ferret@phonewave.net
Cc: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
Petr Vandrovec <VANDROVE@vc.cvut.cz>,
Dana Lacoste <dana.lacoste@peregrine.com>,
linux-kernel@vger.kernel.org
Subject: Re: [OT] Re: Linus's include file strategy redux
Date: Sun, 17 Dec 2000 02:08:06 -0600 (CST) [thread overview]
Message-ID: <14908.29798.413845.663365@wire.cadcamlab.org> (raw)
In-Reply-To: <20001216174351.N3199@cadcamlab.org> <Pine.LNX.3.96.1001216190142.25257A-100000@tarot.mentasm.org>
[ferret@phonewave.net <ferret@phonewave.net>]
> I have not moved or deleted a tree. I do not HAVE a kernel tree in
> the first place. Therefore, nothing for the symlink to point to when
> I install the kernel.
If this is not the machine you compile your kernels on, why are you
compiling your external modules on it?
In any case, at the very least you need a copy of the appropriate
kernel headers. Some distributions have packages for these to match
their kernel image packages. If that's where you got yours, the
packaging should have included the build/ symlink. If it doesn't, file
a bug. And incidentally, also file one if the "kernel headers" package
doesn't come with Makefile, Rules.make, arch/$ARCH/Makefile and
.config . (Those four are very useful for getting your settings right
when compiling external modules.)
If you installed the headers *without* any infrastructure support from
a distribution, then once again I don't think you need "External Module
Compiling for Dummies", and all of the above is *your* job.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-17 8:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 16:56 Petr Vandrovec
2000-12-15 16:00 ` Dana Lacoste
2000-12-15 16:16 ` Eli Carter
2000-12-15 17:31 ` ferret
2000-12-15 18:56 ` Ingo Oeser
2000-12-16 3:37 ` ferret
2000-12-16 6:57 ` Keith Owens
2000-12-16 16:40 ` ferret
2000-12-16 23:43 ` Peter Samuelson
2000-12-17 3:05 ` ferret
2000-12-17 8:08 ` Peter Samuelson [this message]
2000-12-17 20:08 ` ferret
2000-12-18 3:58 ` Peter Samuelson
2000-12-18 19:21 ` ferret
2000-12-15 17:09 Petr Vandrovec
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=14908.29798.413845.663365@wire.cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=VANDROVE@vc.cvut.cz \
--cc=dana.lacoste@peregrine.com \
--cc=ferret@phonewave.net \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--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®