public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: linux-kernel@vger.kernel.org
Cc: dmarkh@cfl.rr.com
Subject: Re: Can't build external module against 2.6.0-test6 kernel
Date: Tue, 14 Oct 2003 07:28:37 -0400	[thread overview]
Message-ID: <3F8BDDE5.84074872@compro.net> (raw)
In-Reply-To: 20031009152350.GA897@mars.ravnborg.org

Sam Ravnborg wrote:
> 
> 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.
> Please follow Documentation/kbuild/modules.txt when building
> external modules.
> 
> Please come back if you continue to have problems.
> 
>         Sam
Ok, I can now build it but I have to hardcode _my_ include directories in the
Makefile like:

/home/markh/work2/pcirtom_tst/driver/Makefile:

EXTRA_CFLAGS = -I/home/markh/work2/pcirtom_tst/include/linux/sys
-I/home/markh/work2/pcirtom_tst/include/linux
-I/home/markh/work2/pcirtom_tst/include

ifneq   ($(KERNELRELEASE),)
        obj-m   += rtom.o
else
        KDIR    := /lib/modules/$(shell uname -r)/build
        PWD     := $(shell pwd)
default:
        $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
endif

My driver tree looks like

driver/
include/
diags/
samples/
library/

I've also tried setting the EXTRA_CFLAGS var in the top makefile but it doesn't
seem to get passed down when the driver is compiled?? I've also tried creating a
link in the driver directory pointing back to the include dir and adjusting the
paths in the EXTRA_CFLAGS to 
-Iinclude/linux/sys -Iinclude/linux -Iinclude to no avail.

Thanks
Mark

  reply	other threads:[~2003-10-14 11:28 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
2003-10-09 15:23 ` Sam Ravnborg
2003-10-14 11:28   ` Mark Hounschell [this message]
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=3F8BDDE5.84074872@compro.net \
    --to=markh@compro.net \
    --cc=dmarkh@cfl.rr.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