All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Pattison <dan.pattison@ethertek.ca>
To: buildroot@busybox.net
Subject: [Buildroot] Configure linux kernel within buildroot
Date: Sat, 12 Sep 2009 08:03:22 -0700	[thread overview]
Message-ID: <4AABB83A.1050705@ethertek.ca> (raw)
In-Reply-To: <90F28E49-FCA0-4AD2-9884-3BEF12EF93DE@gmail.com>

Hi Ben,

Hey, your right, its not in there. In the main make file, if you type 
out make help, it lists some configuration options. I either saw it 
there or read it on the list here somewhere.

Best Regards,
Dan Pattison
EtherTek Circuits 


Ben Coughlan wrote:
> Thanks Dan.  I was hoping there was a 'make linux26-menuconfig'.
>
> I would like to point out that it doesn't appear on the docco you 
> linked (I did spend quite some time scouring it :P).
>
> Cheers,
> Ben Coughlan
>
> On 13/09/2009, at 12:41 AM, Dan Pattison wrote:
>
>> Hi Ben,
>>
>> To build your kernel and images, simply type out    make    from your 
>> buildroot main folder.
>> To configure main buildroot settings type:    make menuconfig
>> To configure kernel settings type:   make linux26-menuconfig
>> To configure busybox type:   make busybox-menuconfig
>> To configure uclibc type:   make uclibc-menuconfig
>>
>> Some good docs can be found here: 
>> http://buildroot.uclibc.org/buildroot.html
>>
>> Best Regards,
>> Dan Pattison
>> EtherTek Circuits
>>
>>
>> Ben Coughlan wrote:
>>> Hi All,
>>>
>>> I'm fairly new to Buildroot and I have a sufficiently newbie 
>>> question to ask.
>>>
>>> How do I configure the kernel buildroot produces?  The first 'make' 
>>> gave me a menuconfig for the kernel but I don't know how to get it 
>>> back or alter the cached config.
>>>
>>> Any hints?
>>>
>>> Regards,
>>> Ben Coughlan
>>> _______________________________________________
>>> buildroot mailing list
>>> buildroot at busybox.net
>>> http://lists.busybox.net/mailman/listinfo/buildroot
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG - www.avg.com Version: 8.5.409 / Virus Database: 
>>> 270.13.91/2363 - Release Date: 09/11/09 09:15:00
>>>
>>>
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com 
> Version: 8.5.409 / Virus Database: 270.13.93/2365 - Release Date: 09/12/09 06:37:00
>
>   

-- 
Dan Pattison
Ethertek Circuits

  reply	other threads:[~2009-09-12 15:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-12 12:13 [Buildroot] Configure linux kernel within buildroot Ben Coughlan
2009-09-12 14:41 ` Dan Pattison
2009-09-12 14:50   ` Ben Coughlan
2009-09-12 15:03     ` Dan Pattison [this message]
2009-09-16  7:18       ` Bernhard Reutner-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=4AABB83A.1050705@ethertek.ca \
    --to=dan.pattison@ethertek.ca \
    --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.