From: Randy Dunlap <randy.dunlap@oracle.com>
To: Pistis Valentino <vale.pistis@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems Compile Misc Module Example
Date: Wed, 11 Aug 2010 16:54:03 -0700 [thread overview]
Message-ID: <20100811165403.6713d206.randy.dunlap@oracle.com> (raw)
In-Reply-To: <AANLkTimGwbP8_fachx9pwTyX1wZxxT1iGrKziWMmxunL@mail.gmail.com>
On Thu, 12 Aug 2010 01:46:27 +0200 Pistis Valentino wrote:
> Hello everyone,
>
> I'm studying how to build kernel modules.
> Right now I have found some strange errors and nothing solutions in the web.
>
> I compiled my kernel module "driver_ase" whose files are driver_ase.h,
> driver_ase.c.
> No errors in compilation, the module is also loaded correctly.
>
> I wrote a small service "service_ase.c" using the kernel module that I created.
> I found a lot of errors.
> the only explanation IMO is that the directory has been renamed from
> "/usr/src/linux-2.6.34.2/include/asm" in
> "/usr/src/linux-2.6.34.2/include/asm-generic", the errors make me
> think that some header file has not yet updated.
>
> You may like this or something wrong?
>
> Could you help me please?
>
> I'm using Debian Sidux with 2.6.34.2 kernel compiled.
>
> In the bottom of the mail has the source codes, and the error.
> It is a bit long error message, sorry!
You need a minimal Makefile.
Please see Documentation/kbuild/modules.txt, section 2. How to build external modules.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-08-11 23:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 23:46 Pistis Valentino
2010-08-11 23:54 ` Randy Dunlap [this message]
2010-08-12 0:16 ` Pistis Valentino
2010-08-12 16:09 ` Pistis Valentino
2010-08-12 16:12 ` Randy Dunlap
2010-08-12 16:25 ` Pistis Valentino
2010-08-12 16:31 ` Randy Dunlap
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=20100811165403.6713d206.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vale.pistis@gmail.com \
/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®