From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Beginner documentation
Date: Tue, 23 Feb 2010 09:36:11 +0100 [thread overview]
Message-ID: <20100223093611.0f5ef6fe@surf> (raw)
In-Reply-To: <3B941116898CDA489B91563DEF88F4B61CAD8E@iwt-server.iwt.local>
Hi Paul,
On Tue, 23 Feb 2010 14:17:40 +1100
"Paul Jones" <Paul.Jones@iwtech.com.au> wrote:
> I'm trying to build a basic buildroot i686 system that I can use for
> learning buildroot. When doing "make linux26-menuconfig" it failed
> because it couldn't find the .config file. From past experience I
> remembered that I have to do make defconfig before that would work, but
> there seems to be no mention of this in the documentation. It would be
> good if something could be added.
I'm not personaly not an user of Buildroot's ability to build the
kernel. Therefore, I'll let others comment on this point.
> I assume http://buildroot.uclibc.org/buildroot.html is the right page to
> be looking at?
Yes, it is the right page to look at. However, documentation is like
software, it might have bugs. Since I'm the author of a large portion
of this documentation and I don't know the kernel build part of
Buildroot, it's very possible that the information in the documentation
isn't exactly correct, or that things have evolved since the
documentation has been written.
If you find any mistakes or inconsistencies, do not hesitate to report
them.
Sincerely,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-02-23 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 3:17 [Buildroot] Beginner documentation Paul Jones
2010-02-23 8:36 ` Thomas Petazzoni [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=20100223093611.0f5ef6fe@surf \
--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