From: Bernd Porr <Bernd.Porr@cn.stir.ac.uk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org, comedi@comedi.org
Subject: Re: compiling external kernel modules (comedi.org)
Date: Sat, 02 Aug 2003 14:10:24 +0100 [thread overview]
Message-ID: <3F2BB840.9060205@cn.stir.ac.uk> (raw)
In-Reply-To: <20030802120756.GA964@mars.ravnborg.org>
Sam,
how can I include the "legal way" includes for comedi? Just now comedi
has set up a "linux/include" path in its directory but I think this not
the elegant way and it also dosn't work right now.
snoopy:/home/bp1/c/usb/2.6/comedi/comedi# make -C
/usr/src/linux-2.6.0-test2 SUBDIRS=$PWD V=1 modules
make: Entering directory `/usr/src/linux-2.6.0-test2'
make -f scripts/Makefile.build obj=scripts
make -f scripts/Makefile.build obj=arch/i386/kernel
arch/i386/kernel/asm-offsets.s
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
*** Warning: Overriding SUBDIRS on the command line can cause
*** inconsistencies
mkdir -p .tmp_versions
make -f scripts/Makefile.build obj=/home/bp1/c/usb/2.6/comedi/comedi
gcc -Wp,-MD,/home/bp1/c/usb/2.6/comedi/comedi/.comedi_fops.o.d
-D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=athlon -Iinclude/asm-i386/mach-default -nostdinc -iwithprefix
include -DMODULE -DKBUILD_BASENAME=comedi_fops
-DKBUILD_MODNAME=comedi_fops -c -o
/home/bp1/c/usb/2.6/comedi/comedi/comedi_fops.o
/home/bp1/c/usb/2.6/comedi/comedi/comedi_fops.c
/home/bp1/c/usb/2.6/comedi/comedi/comedi_fops.c:42:29:
linux/comedidev.h: No such file or directory
/Bernd
P.S.: I'm subscribed...
Sam Ravnborg wrote:
>On Sat, Aug 02, 2003 at 12:53:07PM +0100, Bernd Porr wrote:
>
>
>>Ok. Thanks. Now the bug is that comedi cannot find the file "Rules.make"
>>which is apparently no longer there in 2.6. Is it right that the rules
>>are now integrated in the corresponding makefiles?
>>
>>
>
>The way to find the Makefiles changed during the 2.5 development
>cycle. Now the kbuild Makefile (the one for comedi for example) are
>included from scripts/Makfile.build hereby obsoleting Rules.make.
>
>You will NOT succeed creating a single simple makefile supporting both
>2.4 and 2.6. On the other hand the Makefile are so trivial that creating
>two distinct version should be acceptable?
>
>
>
>>Can you recommend me a Makefile which I can take as a template? Comedi
>>uses some sort of autoconfig and I have to append then the "rules" to
>>the automatically generated makefile.
>>
>>
>
>The most simple Makefile looks like this:
>
>obj-m := comedi.o
>
>No more is actually needed.
>You should get rid of export-objs as well - they are also obsoleted
>in 2.5/2.6.
>
>
>
>
>>Another thing: can a prevent the kernel of generating the "Stage 2"? It
>>would be nice if the kernel doen't need to write to it's own directories
>>if it compiles external modules.
>>
>>
>
>The right fix is to allow you to build a kernel in a directory
>separate from the kernel src. This is WIP - hopefully included in
>mainline within a few weeks.
>
>PS. Please do not cc: subscription only mailing lists.
>
> Sam
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
--
http://www.cn.stir.ac.uk/~bp1/
mailto:bp1@cn.stir.ac.uk
next prev parent reply other threads:[~2003-08-02 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 1:04 compiling external kernel modules (comedi.org) Bernd Porr
2003-08-02 7:04 ` Sam Ravnborg
2003-08-02 11:53 ` Bernd Porr
2003-08-02 12:07 ` Sam Ravnborg
2003-08-02 13:10 ` Bernd Porr [this message]
2003-08-02 23:05 ` Sam Ravnborg
2003-08-11 13:53 ` David Woodhouse
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=3F2BB840.9060205@cn.stir.ac.uk \
--to=bernd.porr@cn.stir.ac.uk \
--cc=comedi@comedi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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).