From: Arjan van de Ven <arjanv@fenrus.demon.nl>
To: immortal1015 <immortal1015@hotpop.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: compiling errors
Date: 01 Oct 2002 20:22:04 +0200 [thread overview]
Message-ID: <1033496525.2575.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20021001180459.E4AD92F8147@smtp-1.hotpop.com>
[-- Attachment #1: Type: text/plain, Size: 376 bytes --]
On Tue, 2002-10-01 at 20:07, immortal1015 wrote:
> I tried to compile the very simple kernel module code as following.
> I compile this code using gcc -c hello.c, but gcc tell me:
> /usr/include/linux /module.h:60 parse error before 'atomic_t'
you are using glibc headers to compile kernel code....
add -I/lib/modules/`uname -r`/build/include
to the gcc flags
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-10-01 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 18:07 compiling errors immortal1015
2002-10-01 18:22 ` Arjan van de Ven [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 18:53 immortal1015
2002-10-01 19:20 ` Richard B. Johnson
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=1033496525.2575.3.camel@localhost.localdomain \
--to=arjanv@fenrus.demon.nl \
--cc=immortal1015@hotpop.com \
--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