From: Edward Macfarlane Smith <snowfire@blueyonder.co.uk>
To: "Ilan S." <ilan_sk@netvision.net.il>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 'hello world' module
Date: Mon, 13 Jun 2005 21:09:44 +0100 [thread overview]
Message-ID: <200506132109.46012.snowfire@blueyonder.co.uk> (raw)
In-Reply-To: <200506111511.02581.ilan_sk@netvision.net.il>
On Saturday 11 June 2005 13:11, Ilan S. wrote:
> Hello dear professionals!
>
> I would be very thankful if anybody prompt me what's wrong.
> I'm trying to build the "Hello world" module from O'Reilly's "Linux device
> drivers" and that is what I get:
>
> [ilanso@Netvision Kernel]$ make -C /home/ilanso/src/linux-2.6.11.11 M=`pwd`
> make: Entering directory `/home/ilanso/src/linux-2.6.11.11'
> Building modules, stage 2.
> MODPOST
> make: Leaving directory `/home/ilanso/src/linux-2.6.11.11'
> [ilanso@Netvision Kernel]$ ls
> hello.c Makefile
> [ilanso@Netvision Kernel]$
>
Hi Ilan,
I've been working through this book too, not sure why it's not working for
you. Have you actually built the kernel in the directory you're pointing it
at? I was able to use the command:
make -C /usr/src/linux M=`pwd`
where my Makefile had
obj-m := eaglenet.o
The makefile I've generally used that works fine (so you can just type make)
was:
ifneq ($(KERNELRELEASE),)
obj-m := eaglenet.o
else
KERNELDIR ?= /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
default:
$(MAKE) -C $(KERNELDIR) M=$(PWD) modules
endif
Where my module was eaglenet.
Regards,
Edward
next prev parent reply other threads:[~2005-06-13 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 12:11 Ilan S.
2005-06-11 18:17 ` Sam Ravnborg
2005-06-11 20:25 ` Jan Engelhardt
2005-06-12 19:17 ` Sam Ravnborg
2005-06-11 19:43 ` Jesper Juhl
2005-06-13 20:09 ` Edward Macfarlane Smith [this message]
2005-06-11 15:53 Nick Warne
[not found] <4egz4-2tj-15@gated-at.bofh.it>
2005-06-11 16:25 ` Robert Hancock
2005-06-11 16:31 ` Jan Engelhardt
2005-06-11 16:54 Nick Warne
2005-06-11 17:06 ` Jan Engelhardt
2005-06-13 17:50 Nick Warne
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=200506132109.46012.snowfire@blueyonder.co.uk \
--to=snowfire@blueyonder.co.uk \
--cc=ilan_sk@netvision.net.il \
--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
all inboxes | Powered by JetHome®