public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: animesh saxena <animesh.saxena@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Compiling kernel 2.6.23.1 HELP
Date: Sat, 13 Oct 2007 19:12:02 +0200	[thread overview]
Message-ID: <20071013171202.GU10199@1wt.eu> (raw)
In-Reply-To: <1192293968.16391.9.camel@localhost.localdomain>

On Sat, Oct 13, 2007 at 10:16:08PM +0530, animesh saxena wrote:
> Hi,
>    I am a kernel newbie, so need some help trying to compile it. 
> I have fedora 7 installed. 
> 
> While compiling it, I get errors as follows.....
> 
>  HOSTCC  scripts/basic/fixdep
> scripts/basic/fixdep.c:107:23: error: sys/types.h: No such file or
> directory
> scripts/basic/fixdep.c:108:22: error: sys/stat.h: No such file or
> directory
> scripts/basic/fixdep.c:109:22: error: sys/mman.h: No such file or
> directory
> scripts/basic/fixdep.c:110:20: error: unistd.h: No such file or
> directory
> scripts/basic/fixdep.c:111:19: error: fcntl.h: No such file or directory
> scripts/basic/fixdep.c:112:20: error: string.h: No such file or
> directory
> scripts/basic/fixdep.c:113:20: error: stdlib.h: No such file or
> directory
> scripts/basic/fixdep.c:114:19: error: stdio.h: No such file or directory

It seems to me that you do not have glibc-devel or any other name it
can have on your distro. It's very likely that after that you will be
missing a few other development packages, but you'll quickly find them
one at a time.

(...)
> On many forums it said I need to have 2.4 kernel headers. I can't
> understand why is it so? Am I missing something?

Possibly that you will also need some random kernel-header-xxxx package,
I don't know how it's packaged. Install the libc headers first to see.

> I used git for getting the latest kernel. 
> 
> git-clone
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

If you're a newbie, you're not encouraged to try building GIT kernels.
They are *very* likely to break during build with nasty errors. You'd
better get the official releases in tar.bz2 form which are know to build
and work for most people.

> Is there something similar for getting kernel headers? Please help. 

not to my knowledge.

Regards,
Willy


  reply	other threads:[~2007-10-13 17:31 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04  3:59 [00/18] Virtual Compound Page Support V2 Christoph Lameter
2007-10-04  3:59 ` [01/18] vmalloc: clean up page array indexing Christoph Lameter
2007-10-04  3:59 ` [02/18] vunmap: return page array passed on vmap() Christoph Lameter
2007-10-04  3:59 ` [03/18] vmalloc_address(): Determine vmalloc address from page struct Christoph Lameter
2007-10-04  3:59 ` [04/18] Vcompound: Smart up virt_to_head_page() Christoph Lameter
2007-10-04  3:59 ` [05/18] Page flags: Add PageVcompound() Christoph Lameter
2007-10-04  3:59 ` [06/18] Vcompound: Update page address determination Christoph Lameter
2007-10-04  3:59 ` [07/18] Vcompound: Add compound_nth_page() to determine nth base page Christoph Lameter
2007-10-13 16:46   ` Compiling kernel 2.6.23.1 HELP animesh saxena
2007-10-13 17:12     ` Willy Tarreau [this message]
2007-10-14  2:35     ` Kristoffer Ericson
2007-10-04  3:59 ` [08/18] GFP_VFALLBACK: Allow fallback of compound pages to virtual mappings Christoph Lameter
2007-10-04  3:59 ` [09/18] Vcompound: GFP_VFALLBACK debugging aid Christoph Lameter
2007-10-04  3:59 ` [10/18] Sparsemem: Use fallback for the memmap Christoph Lameter
2007-10-04  3:59 ` [11/18] Page allocator: Use a higher order allocation for the zone wait table Christoph Lameter
2007-10-04  3:59 ` [12/18] Wait: Allow bit_waitqueue to wait on a bit in a virtual compound page Christoph Lameter
2007-10-04  3:59 ` [13/18] x86_64: Allow fallback for the stack Christoph Lameter
2007-10-04 11:56   ` Andi Kleen
2007-10-04 12:08     ` Peter Zijlstra
2007-10-04 12:25       ` Andi Kleen
2007-10-04 12:30         ` Peter Zijlstra
2007-10-04 17:40         ` Christoph Lameter
2007-10-04 19:20     ` Christoph Lameter
2007-10-04 19:39       ` Rik van Riel
2007-10-04 21:20         ` Christoph Lameter
2007-10-07  7:35           ` Nick Piggin
2007-10-08 17:36             ` Christoph Lameter
2007-10-08 12:55               ` Nick Piggin
2007-10-09 18:39                 ` Christoph Lameter
2007-10-09  8:46                   ` Nick Piggin
2007-10-10  1:26                     ` Christoph Lameter
2007-10-09  9:56                       ` Nick Piggin
2007-10-06 18:53         ` Bill Davidsen
2007-10-04  3:59 ` [14/18] Configure stack size Christoph Lameter
2007-10-04  4:36   ` Arjan van de Ven
2007-10-04  4:43     ` David Miller
2007-10-04 19:34       ` Christoph Lameter
2007-10-04  9:11   ` Andi Kleen
2007-10-04 19:26     ` Christoph Lameter
2007-10-04  3:59 ` [15/18] Fallback for temporary order 2 allocation Christoph Lameter
2007-10-04  3:59 ` [16/18] Virtual Compound page allocation from interrupt context Christoph Lameter
2007-10-04  3:59 ` [17/18] Virtual compound page freeing in " Christoph Lameter
2007-10-04  3:59 ` [18/18] SLUB: Use fallback for table of callers/freers of a slab cache Christoph Lameter

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=20071013171202.GU10199@1wt.eu \
    --to=w@1wt.eu \
    --cc=animesh.saxena@gmail.com \
    --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