From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] building toolchain fails - more details
Date: Wed, 21 Oct 2009 22:54:33 +0200 [thread overview]
Message-ID: <87ljj4piwm.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1531E53627F1F749B4FE809BF2A4EB67013CED64@WETMEX10.loepfe.com> (Noel Vellemans's message of "Wed\, 21 Oct 2009 16\:31\:19 +0200")
>>>>> "Noel" == Vellemans, Noel <Noel.Vellemans@visionBMS.com> writes:
Noel> How to simulate?Just type
Noel> A) 'make at91sam9g20dfc_defconfig' (press enter a couple of times....) {
Noel> but at91sam9260dfc_defconfig has same problem)
Noel> B) make menuconfig
-> kernel -> kernel binary format -> image format : zimage (so
Noel> you can uncheck uboot)
-> Target Filesystem options -> de-select 'uboot'. (has nothing to
Noel> do with this prob but has some other issue's)
-> pakage selcetion - > de-select 'at'
FYI, the above builds for me with latest git.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-10-21 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7.1256126402.21246.buildroot@busybox.net>
2009-10-21 14:31 ` [Buildroot] building toolchain fails - more details Vellemans, Noel
2009-10-21 18:31 ` Peter Korsgaard
2009-10-21 20:54 ` Peter Korsgaard [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=87ljj4piwm.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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