From: Muli Ben-Yehuda <mulix@mulix.org>
To: Mark Hounschell <markh@compro.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Can't build external module against 2.6.0-test6 kernel
Date: Thu, 9 Oct 2003 13:40:23 +0200 [thread overview]
Message-ID: <20031009114023.GI4699@actcom.co.il> (raw)
In-Reply-To: <3F8544DF.85E7CA81@compro.net>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
On Thu, Oct 09, 2003 at 07:22:07AM -0400, Mark Hounschell wrote:
> I'm trying to build a driver external to the kernel. I'm running 2.6.0-test6
> kernel.
> It appears to me (I'm probably wrong) that there is a kernel include
> file issue.
>
> gcc -c rtom.c -D__KERNEL__ -DMODULE -DDEBUG -DDEBUG_LEVEL=6
> -I/lib/modules/2.6.0-test6/build/include -I../include/linux/sys
> -I../include/linux -I../include -O -o rtom
This compilation command line dos not look like it came from the kerel
build system? If indeed you're using your own build system, please use
the kernel's build system to compile external modules. See
Documentation/kbuild/* for details, as well as lwn.net's "Compling
External Modules" article - http://lwn.net/Articles/21823/. I'm
guessing that you do not have something set up properly that the
kernel's build system would've set up for you.
--
Muli Ben-Yehuda
http://www.mulix.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-09 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 11:22 Can't build external module against 2.6.0-test6 kernel Mark Hounschell
2003-10-09 11:40 ` Muli Ben-Yehuda [this message]
2003-10-09 15:23 ` Sam Ravnborg
2003-10-14 11:28 ` Mark Hounschell
2003-10-14 17:44 ` Sam Ravnborg
2003-10-14 18:31 ` Mark Hounschell
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=20031009114023.GI4699@actcom.co.il \
--to=mulix@mulix.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
/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