From: "Murali Therthala" <MuraliT@prodigy.net>
To: <linux-kernel@vger.kernel.org>
Subject: Compilation Error with a Dynamic Module
Date: Sun, 20 Oct 2002 15:22:46 -0400 [thread overview]
Message-ID: <001301c2786e$1303b160$eef13ccc@kamalnara317> (raw)
Hi All,
I am trying to compile a dynamic module shown below that creates a readable
procs entry.
I invoke gcc as follows.
gcc -Wall -o2 -DMODULE -D_KERNEL_ -DLINUX -I
/lib/modules/`uname -r`\build/modules -c fMod3.c
and I get a whole bunch of errors with procfs.h.
/lib/modules/2.4.18-4GB/build/include/linux/proc_fs.h:47: parse error before
`off_t'
/lib/modules/2.4.18-4GB/build/include/linux/proc_fs.h:50: warning: `struct
file' declared inside parameter list
............................................................................
............................................................
............................................................................
............................................................
Could any of you offer me any hints to resolve this problem? I am using SUSE
with Kernel 2.4.18-4GB.
Thanks in advance for any feedback. Please see the source below.
Murali
----------------------------------------------------------------------------
---------------------------------
#include <linux/module.h>
#include <linux/kernel.h>
#include <linux/init.h>
#include <linux/proc_fs.h>
#include <linux/sched.h>
#include <asm/uaccess.h>
#define MODULE_VERSION "1.0"
#define MODULE_NAME "My_procfs_example"
#define FOOBAR_LEN 8
struct fb_data_t
{
char name[FOOBAR_LEN + 1];
char value[FOOBAR_LEN + 1];
};
static struct proc_dir_entry *example_dir,*foo_file;
struct fb_data_t foo_data;
static int proc_read_foo(char *page,char **start,off_t off,int count,int
*eof,void *data)
{
int len;
struct fb_data_t *fb_data = (struct fb_data_t *)data;
MOD_INC_USE_COUNT;
len = sprintf(page, "%s = '%s'\n",fb_data->name, fb_data->value);
MOD_DEC_USE_COUNT;
return len;
}
static int __init init_procfs_example(void)
{
int rv = 0;
/* create directory */
example_dir = proc_mkdir(MODULE_NAME, NULL);
if(example_dir == NULL)
{
rv = -ENOMEM;
goto out;
}
example_dir->owner = THIS_MODULE;
foo_file = create_proc_entry("foo", 0644, example_dir);
if(foo_file == NULL)
{
rv = -ENOMEM;
goto no_foo;
}
strcpy(foo_data.name, "foo");
strcpy(foo_data.value, "foo");
foo_file->data = &foo_data;
foo_file->read_proc = proc_read_foo;
foo_file->write_proc = NULL;
foo_file->owner = THIS_MODULE;
printk(KERN_INFO "%s %s initialised\n",MODULE_NAME, MODULE_VERSION);
return 0;
no_foo:
remove_proc_entry("jiffies", example_dir);
out:
return rv;
}
static void __exit cleanup_procfs_example(void)
{
remove_proc_entry("foo", example_dir);
remove_proc_entry(MODULE_NAME, NULL);
printk(KERN_INFO "%s %s removed\n",MODULE_NAME, MODULE_VERSION);
}
module_init(init_procfs_example);
module_exit(cleanup_procfs_example);
MODULE_AUTHOR("XYZ");
MODULE_DESCRIPTION("A procfs example");
EXPORT_NO_SYMBOLS;
next reply other threads:[~2002-10-20 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-20 19:22 Murali Therthala [this message]
2002-10-20 20:43 ` Sam Ravnborg
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='001301c2786e$1303b160$eef13ccc@kamalnara317' \
--to=muralit@prodigy.net \
--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
all inboxes | Powered by JetHome®