public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lei Yang <leiyang@nec-labs.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Kernel Newbies Mailing List <kernelnewbies@nl.linux.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problems compiling kernel modules
Date: Sat, 21 Aug 2004 15:45:38 -0400	[thread overview]
Message-ID: <4127A662.2090708@nec-labs.com> (raw)
In-Reply-To: <20040821214402.GA7266@mars.ravnborg.org>

Sam Ravnborg wrote:
> On Sat, Aug 21, 2004 at 03:24:12PM -0400, Lei Yang wrote:
> 
>>Hi all,
>>
>>I was trying to compile a kernel module with kbuild. The module 'test.c' 
>>include a header file 'fred.h' and there is a "#include <stdio.h>" in 
>>'fred.h'.
>>
>>Makefile looks like:
>>
>>------------------------------------------------------------------------
>>ifneq ($(KERNELRELEASE),)
>>obj-m       := test.o
>>
>>else
>>KDIR        := /usr/src/linux
>>PWD         := $(shell pwd)
>>
>>default:
>>	$(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
>>	
>>
>>clean:
> 
> For 2.6.7 (or 2.6.6) you do not need to specify your own clean: rule.
> 
> 
>>But upon compiling, there would be errors like this:
>>In file included from /home/lei/test.c:49:
>>/home/lei/fred.h:4:19: stdio.h: No such file or directory
> 
> The kernel does not provide you with a stdio.h header, so therefore you
> cannot find it neither use functionality from it.

You mean I can't use stdio.h at all?

But what if I really need to? Is there anything I can do?

> 	Sam

  reply	other threads:[~2004-08-21 19:46 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 [this message]
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
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=4127A662.2090708@nec-labs.com \
    --to=leiyang@nec-labs.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox