public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Srinivas G." <srinivasg@esntechnologies.co.in>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Small problem, Can anybody help me?
Date: Thu, 6 May 2004 15:33:21 +0100	[thread overview]
Message-ID: <20040506143321.GA8430@redhat.com> (raw)
In-Reply-To: <1118873EE1755348B4812EA29C55A97222F512@esnmail.esntechnologies.co.in>

On Thu, May 06, 2004 at 07:31:56PM +0530, Srinivas G. wrote:

 > I compiled it under same kernel version that is 2.4.18-3. It was showing
 > the following errors.
 > 
 > In file included from hello.c:2:
 > /usr/include/linux/module.h:60: parse error before `atomic_t'
 > /usr/include/linux/module.h:60: warning: no semicolon at end of struct
 > or union
 > /usr/include/linux/module.h:60: warning: no semicolon at end of struct
 > or union
 > /usr/include/linux/module.h:62: parse error before `}'
 > /usr/include/linux/module.h:62: warning: data definition has no type or
 > storage class
 > /usr/include/linux/module.h:91: parse error before `}'

You're trying to include userspace headers into a kernel module.
This won't fly.

 > The errors came due to a mistake in linux header file. Is it so...
 > 
 > Thanks in advance for any help you can come up with.

Last week you claimed "Linux has broken spinlocks", this week "broken includes".
I suggest a trip to http://www.kernelnewbies.org/ may be in order
before you tackle anything more complicated than a helloworld module.

		Dave


  parent reply	other threads:[~2004-05-06 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-06 14:01 Small problem, Can anybody help me? Srinivas G.
2004-05-06 14:28 ` Erik Mouw
2004-05-06 17:27   ` David Woodhouse
2004-05-06 14:33 ` Dave Jones [this message]
2004-05-06 15:47 ` 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=20040506143321.GA8430@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivasg@esntechnologies.co.in \
    /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