Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to build Kernel 2.6.x
Date: Wed, 14 Nov 2012 15:31:58 +0100	[thread overview]
Message-ID: <20121114153158.5de351df@skate> (raw)
In-Reply-To: <k7vnmj$27j$1@ger.gmane.org>

Dear woody,

On Wed, 14 Nov 2012 17:19:15 +0800, woody wrote:

> I want to build kernel version 2.6.16 for ARM (s3c2410).  The 2.6.16 is

Why 2.6.16 ? This is prehistory.
 
> not listed in either tool chains kernel headers options list or kernel 
> version options list.  What I can do is manual specify the version via 
> the buildroot menus.  However, it then failed in a stable of buidling 
> toolchain, it complains that there is no a '.config' found under the 
> kernel source directory and also not found the "headers_install" targets.
> 
> I've already manually downloaded the 2.6.16 tarball to the correct 
> location that can be found by buildroot.
> 
> So, what should I do?  Is may method wrong?

Please post your Buildroot .config file and put your entire build log
on some pastebin site (http://pastebin.com for example).

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-11-14 14:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14  9:19 [Buildroot] How to build Kernel 2.6.x woody
2012-11-14 14:31 ` Thomas Petazzoni [this message]
2012-11-14 14:47   ` Yann E. MORIN
2012-11-14 14:57     ` Woody Wu
2012-11-14 15:03       ` Thomas Petazzoni
2012-11-14 15:13         ` Woody Wu
2012-11-14 15:24           ` Thomas Petazzoni
2012-11-14 15:28             ` Richard Braun
2012-11-14 15:25           ` Jeremy Rosen
2012-11-14 15:07   ` Woody Wu

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=20121114153158.5de351df@skate \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox