From: Lei Yang <leiyang@nec-labs.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Kernel Newbies Mailing List <kernelnewbies@nl.linux.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problems compiling kernel modules
Date: Mon, 23 Aug 2004 10:10:16 -0400 [thread overview]
Message-ID: <4129FAC8.3040502@nec-labs.com> (raw)
In-Reply-To: <1093121824.854.167.camel@krustophenia.net>
Hi friends,
I've askeed questions about errors compiling kernel modules caused by
including <stdio.h> and got some very helpful info here.
I changed those I/O stream and file operation in the code and get the
module compiled, however, there would be warnings like
In file included from /home/lei/modules/test.c:49:
/home/lei/modules/Kcomp.h:21: warning: function declaration isn't a
prototype
/home/lei/modules/Kcomp.h:27: warning: function declaration isn't a
prototype
/home/lei/modules/Kcomp.h:69: warning: function declaration isn't a
prototype
And the no prototype fuction looks like
int preset() // with no arguments
{
p = &nodes[0][0];
return 0;
}
So when I tried to install the module with insmod ./test.ko ,
there would be an error,
insmod: error inserting './test.ko': -1 Unknown symbol in module
Could anyone tell me what is wrong here? Is that because of the no
prototype function declaration?
TIA
Lei
Lee Revell wrote:
> On Sat, 2004-08-21 at 16:46, Lei Yang wrote:
>
>>What about multi-file module?
>>
>>Say test.c doesn't include stdio.h, while there is some other .c file
>>which is to be compiled and linked into test.ko, include stdio?
>>
>>Would that work?
>>
>
>
> Are you just trying to print from a kernel module? Use printk.
>
> The kernel does not really have its own standard input and standard
> output - the kernel manages those things for processes.
>
> Lee
>
next prev parent reply other threads:[~2004-08-23 14:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 19:24 Problems compiling kernel modules Lei Yang
2004-08-21 21:44 ` Sam Ravnborg
2004-08-21 19:45 ` Lei Yang
2004-08-21 20:05 ` viro
2004-08-21 20:13 ` Lee Revell
2004-08-21 21:50 ` Sam Ravnborg
2004-08-21 19:55 ` Lei Yang
2004-08-21 20:46 ` Lei Yang
2004-08-21 20:57 ` Lee Revell
2004-08-23 14:10 ` Lei Yang [this message]
2004-08-23 14:29 ` Richard B. Johnson
2004-08-23 14:39 ` Lei Yang
2004-08-23 14:52 ` Richard B. Johnson
2004-08-23 15:04 ` Lei Yang
2004-08-23 15:20 ` Richard B. Johnson
2004-08-23 15:25 ` Sam Ravnborg
2004-08-23 15:44 ` Lei Yang
2004-08-23 16:21 ` Alan Cox
2004-08-23 14:52 ` Alan Cox
2004-08-23 15:48 ` Andreas Schwab
2004-08-21 21:11 ` Alex Goddard
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=4129FAC8.3040502@nec-labs.com \
--to=leiyang@nec-labs.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=sam@ravnborg.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.