From: brunoguedes@gmail.com (Bruno Guedes Souto)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Fwd: My simple kernel module wont compile
Date: Fri, 12 Sep 2014 18:29:56 +0000 (UTC) [thread overview]
Message-ID: <loom.20140912T201416-827@post.gmane.org> (raw)
In-Reply-To: 5412AAB0.9010401@gmail.com
testlaster <testlaster <at> gmail.com> writes:
>
>
> Yes I did run sudo apt-get install build-essential
> linux-headers-$(uname -r) to download the necessary headers. I also
> ran an apt-get for source files and it did install a whole bunch of
> them but Im not under the impression that you actually need the
> source files as well since they suppose to come with the OS?
No, many distributions don't come with the source files.
> The thing its complaining about... unistd_32.h appears to really be
> missing. Could this be because of a 64Bit version of the OS?
No, I've ran your code last night on a 64bit machine of mine and beside some
compiling errors due to wrong syntax and function declaration it was all
fine.
> Maybes
> just doesnt install it because its not necessary. But that wouldnt
> make sense because in unistd.h the only include there is will be the
> unistd_32.h and nowhere inside stands anything of
> #include<unistd_64.h>
It seems to me, you are just missing the necessary tools from your
distribution
to do the kind of work you want to do. Try a google search on your distro
+ kernel development and you probably will find what you need. Usually what
you
must get are the linux-source, kernel-devel and kernel-tools packages.
Regards
Bruno Guedes Souto
next prev parent reply other threads:[~2014-09-12 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 11:12 My simple kernel module wont compile testlaster
2014-09-11 13:49 ` Gustavo Bittencourt
2014-09-11 14:13 ` testlaster
2014-09-11 15:06 ` Fwd: " Gustavo Bittencourt
2014-09-12 8:11 ` testlaster
2014-09-12 18:29 ` Bruno Guedes Souto [this message]
2014-09-11 15:11 ` Valdis.Kletnieks at vt.edu
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=loom.20140912T201416-827@post.gmane.org \
--to=brunoguedes@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 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.