From: John Levon <levon@movementarian.org>
To: linux-kernel@vger.kernel.org
Subject: Re: unknown symbols loading modules under 2.6.x
Date: Mon, 22 Sep 2003 17:49:16 +0100 [thread overview]
Message-ID: <20030922164916.GA12729@compsoc.man.ac.uk> (raw)
In-Reply-To: <20030922163432.GA3208@mars.ravnborg.org>
On Mon, Sep 22, 2003 at 06:34:32PM +0200, Sam Ravnborg wrote:
> Also make sure that you use kbuild when compiling your module.
Talking of which, how hard would it be to fix make clean and make
modules_install for this ?
Current make clean with SUBDIRS set still cleans out the entire kernel
tree, and modules_install wipes out the entire target modules directory.
It would be nice to see at least the latter fixed so there's a simple
way for building modules against 2.6 series (especially since it's
already way nicer than the contortions for 2.2 and 2.4).
regards
john
--
Khendon's Law:
If the same point is made twice by the same person, the thread is over.
next prev parent reply other threads:[~2003-09-22 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 16:07 unknown symbols loading modules under 2.6.x Kirk Reiser
2003-09-22 16:18 ` Randy.Dunlap
2003-09-22 16:34 ` Sam Ravnborg
2003-09-22 16:49 ` John Levon [this message]
2003-09-22 19:56 ` Sam Ravnborg
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=20030922164916.GA12729@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--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