All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe <zentrale.at.work@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] kernel header 2.6.12
Date: Fri, 30 Nov 2007 12:33:05 +0100	[thread overview]
Message-ID: <474FF4F1.2090004@gmail.com> (raw)
In-Reply-To: <BAY131-W15D44FED3FDE6342B12D24E2710@phx.gbl>

You have to enable "Show obsolete/deprecated features".

Greetz

saravanan chanemouganandam schrieb:
> Hi all,
>  
> I have downloaded the latest version of buildroot to build toolchain and small rootfs for my arm (armv5te) target pxa270. The board runs  linux 2.6.16 version and I want to replace the existing glibc rootfs with a small uclibc rootfs. 
>  
> Buildroot's make menuconfig doesn't show kernel header version 2.6.12 to build toolchain. Can anybody tell me how can I choose kernel header version 2.6.12 in toolchain option to build correct toolchain? 
>  
> will doing make DEFAULT_KERNEL_HEADERS=2.6.12 correcty build the toolchain arm-linux-uclibc-*?
>  
> Thanks
> sara
>  
>  
>  
> _________________________________________________________________
> Tried the new MSN Messenger? It?s cool! Download now.
> http://messenger.msn.com/Download/Default.aspx?mkt=en-in
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot


-- 
Sepp "ZaP" Holzmayr

please reply to:
zentrale.at.work at gmail.com

watch out for:
www.rocksociety.de

  reply	other threads:[~2007-11-30 11:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 11:12 [Buildroot] kernel header 2.6.12 saravanan chanemouganandam
2007-11-30 11:33 ` Joe [this message]
2007-11-30 14:46   ` saravanan chanemouganandam

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=474FF4F1.2090004@gmail.com \
    --to=zentrale.at.work@gmail.com \
    --cc=buildroot@busybox.net \
    /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.