From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/8] documentation: Reword introduction about external toolchains
Date: Wed, 24 Nov 2010 16:33:04 +0100 [thread overview]
Message-ID: <877hg268jz.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <6f4f89fb50275d9eed3bff44bb874649ccd81457.1290609511.git.thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Wed, 24 Nov 2010 15:38:40 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Thomas> ---
Thomas> docs/buildroot.html | 23 ++++++++++++++++-------
Thomas> 1 files changed, 16 insertions(+), 7 deletions(-)
Thomas> diff --git a/docs/buildroot.html b/docs/buildroot.html
Thomas> index 9ea0374..a7dd8d6 100644
Thomas> --- a/docs/buildroot.html
Thomas> +++ b/docs/buildroot.html
Thomas> @@ -715,13 +715,22 @@ endif
Thomas> <h2 id="external_toolchain">Using an external toolchain</h2>
Thomas> - <p>It might be useful not to use the toolchain generated by
Thomas> - Buildroot, for example if you already have a toolchain that is known
Thomas> - to work for your specific CPU, or if the toolchain generation feature
Thomas> - of Buildroot is not sufficiently flexible for you (for example if you
Thomas> - need to generate a system with <i>glibc</i> instead of
Thomas> - <i>uClibc</i>). Buildroot supports using an <i>external
Thomas> - toolchain</i>.</p>
Thomas> + <p>It might be useful not to use an already existing toolchain,
Funny ;) --^
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-11-24 15:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 14:38 [Buildroot] [pull request] Pull request for branch for-2010.11/doc-updates Thomas Petazzoni
2010-11-24 14:38 ` [Buildroot] [PATCH 1/8] documentation: clarify Buildroot steps Thomas Petazzoni
2010-11-24 14:38 ` [Buildroot] [PATCH 2/8] documentation: Tell not to use make -jN Thomas Petazzoni
2010-11-24 14:38 ` [Buildroot] [PATCH 3/8] documentation: Remove mention of gcc 3.x Thomas Petazzoni
2010-11-24 14:38 ` [Buildroot] [PATCH 4/8] documentation: Update details about external toolchains Thomas Petazzoni
2010-11-24 14:38 ` [Buildroot] [PATCH 5/8] documentation: Mention which external toolchains we tested Thomas Petazzoni
2010-11-24 14:38 ` [Buildroot] [PATCH 6/8] documentation: Reword introduction about external toolchains Thomas Petazzoni
2010-11-24 14:48 ` Yann E. MORIN
2010-11-24 15:39 ` Thomas Petazzoni
2010-11-24 15:33 ` Peter Korsgaard [this message]
2010-11-24 14:38 ` [Buildroot] [PATCH 7/8] documentation: Document the GIT/SVN download capabilities Thomas Petazzoni
2010-11-24 14:38 ` [Buildroot] [PATCH 8/8] documentation: Mention the fact that the skeleton location can be configured Thomas Petazzoni
2010-11-24 15:42 ` [Buildroot] [pull request] Pull request for branch for-2010.11/doc-updates Peter Korsgaard
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=877hg268jz.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