From: Javier Martinez Canillas <martinez.javier@gmail.com>
To: ratheesh kannoth <ratheesh.ksz@gmail.com>
Cc: Jean-Marc Simohand <jeanmarc.simohand@maxim-ic.com>,
linux-newbie <linux-newbie@vger.kernel.org>,
"linux-c-programming@vger.kernel.org"
<linux-c-programming@vger.kernel.org>
Subject: Re: header files missing
Date: Mon, 12 Dec 2011 15:59:16 +0100 [thread overview]
Message-ID: <CAAwP0s08xMLYrp2X0_4ktx+9apEYz5HfTCpT=fmrwnmcO7iULA@mail.gmail.com> (raw)
In-Reply-To: <CAGZFCEFiYf88nhEeYUGmHOJ5TXXgC3F5WOC6xx2CsofE5GEL9Q@mail.gmail.com>
On Mon, Dec 12, 2011 at 3:38 PM, ratheesh kannoth
<ratheesh.ksz@gmail.com> wrote:
> On Mon, Dec 12, 2011 at 8:04 PM, Jean-Marc Simohand
> <jeanmarc.simohand@maxim-ic.com> wrote:
>>
>> Hi Ratheesh,
>> did you install the "build-essential package" ?
>>
>> sudo apt-get install build-essential
>>
>
> i don't have apt-get or yum. its a custom compiled kernel.
>
I think you are mixing concepts here. stdio.h and others are ANSI C
user-space library headers. These comes with a C library like glibc.
The kernel has nothing to do about it. Unless you want to compile
user-space applications that use kernel headers.
Best regards,
--
Javier Martínez Canillas
(+34) 682 39 81 69
Barcelona, Spain
--
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-12-12 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 14:16 header files missing ratheesh kannoth
2011-12-12 14:34 ` Jean-Marc Simohand
2011-12-12 14:38 ` ratheesh kannoth
2011-12-12 14:59 ` Javier Martinez Canillas [this message]
2011-12-12 15:01 ` Jonathan Isom
2011-12-12 15:04 ` Renjith Gopinadhan
2011-12-14 13:18 ` Glynn Clements
2011-12-14 14:14 ` Aniruddha Bhattacharyya
2011-12-14 15:15 ` Yichao Yu
2011-12-12 15:03 ` Jean-Marc Simohand
2011-12-14 15:20 ` Yichao Yu
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='CAAwP0s08xMLYrp2X0_4ktx+9apEYz5HfTCpT=fmrwnmcO7iULA@mail.gmail.com' \
--to=martinez.javier@gmail.com \
--cc=jeanmarc.simohand@maxim-ic.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=ratheesh.ksz@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).