Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] 2.6.16 kernel headers
Date: Mon, 4 Dec 2006 17:26:26 +0100	[thread overview]
Message-ID: <20061204162626.GA25253@aon.at> (raw)
In-Reply-To: <20061204152218.171330@gmx.net>

On Mon, Dec 04, 2006 at 04:22:18PM +0100, Real.Magic at gmx.de wrote:
>I am going to use Linux kernel 2.6.16 for PowerPC from ftp://ftp.denx.de/pub/linux, but I could not found the matching kernel header files in buildroot menu.
>In this menu only 2.6.12 and 2.6.18 are available.

buildroot has sanitized kernel headers up to 2.6.12 (from Mazur) or the
headers_install kernel headers from 2.6.19.
>
>How can I build the toolchain for 2.6.16 kernel?
select 2.6.12 headers.
You can run about any kernel you want.

HTH,

  reply	other threads:[~2006-12-04 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-04 15:22 [Buildroot] 2.6.16 kernel headers Real.Magic at gmx.de
2006-12-04 16:26 ` Bernhard Fischer [this message]
     [not found]   ` <20061204163723.76850@gmx.net>
2006-12-04 17:23     ` Bernhard Fischer

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=20061204162626.GA25253@aon.at \
    --to=rep.nop@aon.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox