From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] How do I configure the kernel?
Date: Mon, 23 Nov 2009 21:56:07 +0000 (UTC) [thread overview]
Message-ID: <hef0dm$mr0$1@ger.gmane.org> (raw)
In-Reply-To: b680c1c10911231350p7fd9f9beu6dda424828879727@mail.gmail.com
On 2009-11-23, Nicholas Walton <nwalton@aplopteng.com> wrote:
>>> That does work, but a more direct way would be to do the linux
>>> configuration through buildroot.
>>>
>>> ~/buildroot % make menuconfig
>>> ~/buildroot % make linux26-menuconfig
>>> ~/buildroot % cp old-linux.config ?output/build/linux-$version/.config
>>> ~/buildroot % make linux26-$either_config
>>> ~/buildroot % make
>>
>> What is $either_config?
>
> menuconfig or oldconfig. Oldconfig will prompt you with new
> options, menuconfig assumes you know what you need to change
> from defaults.
While make linux26-menuconfig works, I could never get "make
linux26-oldconfig" to work. That's why I resorted to the
method I described.
$ make linux26-oldconfig
make: *** No rule to make target linux26-oldconfig'. Stop.
--
Grant Edwards grante Yow! Are you selling NYLON
at OIL WELLS?? If so, we can
visi.com use TWO DOZEN!!
prev parent reply other threads:[~2009-11-23 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 22:23 [Buildroot] How do I configure the kernel? Grant Edwards
[not found] ` <b680c1c10911201430s25dadd6aj8d1c48afaff91445@mail.gmail.com>
2009-11-20 22:35 ` Nicholas Walton
2009-11-21 5:00 ` Grant Edwards
2009-11-21 18:20 ` Nicholas Walton
2009-11-22 20:44 ` Peter Korsgaard
2009-11-23 19:10 ` Grant Edwards
2009-11-23 20:01 ` Grant Edwards
2009-11-23 20:39 ` Nicholas Walton
2009-11-23 21:41 ` Grant Edwards
2009-11-23 21:50 ` Nicholas Walton
2009-11-23 21:56 ` Grant Edwards [this message]
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='hef0dm$mr0$1@ger.gmane.org' \
--to=grant.b.edwards@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox