From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: External module Makefile with generated C file
Date: Sat, 27 Jan 2007 16:15:16 -0200 [thread overview]
Message-ID: <45BB96B4.30907@redhat.com> (raw)
Sam,
I'm trying to create a external module that involves generating
one of the source files needed for
the module, I'm using this Makefile:
[acme@filo ctracer_example]$ cat Makefile
obj-m := ctracer.o
ctracer-y := ctracer_methods.o ctracer_jprobe.o
CLASS=sock
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
default:
$(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
clean:
rm -f *.mod.c *.ko *.o ctracer_methods.c
# Files generated that shall be removed upon make clean
clean-files := ctracer_methods.c
ctracer_methods.o: ctracer_methods.c
ctracer_methods.c:
ctracer /usr/lib/debug/lib/modules/$(shell uname -r)/vmlinux
$(CLASS) > ctracer_methods.c
[acme@filo ctracer_example]$
But I get this as the result:
[acme@filo ctracer_example]$ make
make -C /lib/modules/2.6.19-1.2895.fc6/build
SUBDIRS=/home/acme/git/pahole/ctracer_example modules
make[1]: Entering directory `/usr/src/kernels/2.6.19-1.2895.fc6-i686'
make[2]: *** No rule to make target
`/home/acme/git/pahole/ctracer_example/ctracer_methods.o', needed by
`/home/acme/git/pahole/ctracer_example/ctracer.o'. Stop.
make[1]: *** [_module_/home/acme/git/pahole/ctracer_example] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.19-1.2895.fc6-i686'
make: *** [default] Error 2
[acme@filo ctracer_example]$
What is the stupid thing I'm doing? :-)
- Arnaldo
next reply other threads:[~2007-01-27 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 18:15 Arnaldo Carvalho de Melo [this message]
2007-01-27 18:30 ` External module Makefile with generated C file Jan Engelhardt
2007-01-27 18:42 ` Arnaldo Carvalho de Melo
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=45BB96B4.30907@redhat.com \
--to=acme@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.