From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] More newb questions
Date: Tue, 22 Jan 2008 09:37:04 +0100 [thread overview]
Message-ID: <20080122083704.GA30062@aon.at> (raw)
In-Reply-To: <030f01c85c89$b3e08590$040514ac@atmel.com>
On Mon, Jan 21, 2008 at 11:20:56PM +0100, Ulf Samuelsson wrote:
>> Is it possible to used menuconfig to edit a linux config file for an Arm
>> target? Or do I have to edit the config file by hand? Whenever I try to
>> do this, it defaults to an arch/I386/Kconfig and I get a bunch of
>> non-existent parameters.
>
>No, It is porbably best to enter the linux directory and do
>$ make ARCH=<arch> xconfig
This is wrong.
See docs/README.
>
>Once you have done that, you can go back to the buildroot top directory and do
>
>$ make saveconfig
>The result will be stored in "local"
>
>
>> I still can't figure out why a -rt9 keeps getting appended to the
>> 2.6.22.1 directory name created in the lib/modules directory. My
>> buildroot keeps failing because there is no 2.6.22.1 directory to put
>> modules in. Should I not be using a real-time kernel? Or is this some
>> kind of buildroot bug??
>
>Check if you are adding real time patches (defined in the kernel headers section of menuconfig)
>
>Best Regards
>Ulf Samuelsson ulf at atmel.com
>Atmel Nordic AB
>Mail: Box 2033, 174 02 Sundbyberg, Sweden
>Visit: Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
>Phone +46 (8) 441 54 22 Fax +46 (8) 441 54 29
>GSM +46 (706) 22 44 57
>
>
>_______________________________________________
>buildroot mailing list
>buildroot at uclibc.org
>http://busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2008-01-22 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 15:25 [Buildroot] More newb questions Tim Barr
2008-01-21 22:20 ` Ulf Samuelsson
2008-01-22 8:37 ` Bernhard Fischer [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=20080122083704.GA30062@aon.at \
--to=rep.dot.nop@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