From: vic.lix10@gmail.com (Vic)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Char driver
Date: Sat, 7 May 2011 07:20:05 -0700 [thread overview]
Message-ID: <BANLkTi=yQhTTvJyN60XPV4w6hP8QfgAiGA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimEx2k5pni98ysrO946QDcv5aFRMQ@mail.gmail.com>
Problem is your "/lib/modules/2.6.35.12-90.fc14.i686/" path was given out by
"uname -r".
On Sat, May 7, 2011 at 6:25 AM, Aravind Vijayan <aravind1123@gmail.com>wrote:
> Hi all,
>
> i am totally newbie to drivers,but i like to deal with them . I have
> a code here:http://pastebin.com/9YsJetek
>
>
> when i try to make it,
>
> /*make file*/
> obj-m +=memory.o
>
> all:
> make -C /lib/modules/$(shell uname -r)/build M=$(pwd) modules
> clean:
> make -C /lib/modules/$(shell uname -r)/build M=$(pwd) clean
> /*End*/
>
>
> i got some error:
> make -C /lib/modules/2.6.35.12-90.fc14.i686/build M= modules
> make[1]: Entering directory `/usr/src/kernels/2.6.35.12-90.fc14.i686'
> CHK include/linux/version.h
> CHK include/generated/utsrelease.h
> make[2]: *** No rule to make target `missing-syscalls'. Stop.
> make[1]: *** [prepare0] Error 2
> make[1]: Leaving directory `/usr/src/kernels/2.6.35.12-90.fc14.i686'
> make: *** [all] Error 2
>
> how can i fix this....
>
> Thanks in advance.
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110507/f2facce4/attachment.html
next prev parent reply other threads:[~2011-05-07 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 13:25 Char driver Aravind Vijayan
2011-05-07 14:20 ` Vic [this message]
2011-05-08 8:36 ` Mulyadi Santosa
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='BANLkTi=yQhTTvJyN60XPV4w6hP8QfgAiGA@mail.gmail.com' \
--to=vic.lix10@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).