From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] docs/manual: slightly improve faq entry about compiler on target
Date: Wed, 8 Oct 2014 22:23:13 +0200 [thread overview]
Message-ID: <20141008202313.GC4718@free.fr> (raw)
In-Reply-To: <1412799410-19667-1-git-send-email-thomas.petazzoni@free-electrons.com>
Thomas, All,
On 2014-10-08 22:16 +0200, Thomas Petazzoni spake thusly:
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> docs/manual/faq-troubleshooting.txt | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/docs/manual/faq-troubleshooting.txt b/docs/manual/faq-troubleshooting.txt
> index 7195234..693028c 100644
> --- a/docs/manual/faq-troubleshooting.txt
> +++ b/docs/manual/faq-troubleshooting.txt
> @@ -35,7 +35,9 @@ target_ would be stopped from the Buildroot-2012.11 release because:
> * this feature was only available for Buildroot toolchains;
> * Buildroot mostly targets _small_ or _very small_ target hardware
> with limited resource onboard (CPU, ram, mass-storage), for which
> - compiling does not make much sense.
> + compiling on the target does not make much sense;
I'd phrase that differently:
Buildroot mostly targets _small_ or _very small_ target hardware
with limited resource onboard (CPU, ram, mass-storage), on which
compiling does not much much sense.
Note: s/for/on/
Regards,
Yann E. MORIN.
> +* Buildroot aims at easing the cross-compilation, making native
> + compilation on the target unnecessary.
>
> If you need a compiler on your target anyway, then Buildroot is not
> suitable for your purpose. In such case, you need a _real
> --
> 2.0.0
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-10-08 20:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 20:16 [Buildroot] [PATCH 1/2] docs/manual: slightly improve faq entry about compiler on target Thomas Petazzoni
2014-10-08 20:16 ` [Buildroot] [PATCH 2/2] docs/manual: add FAQ entry about speeding up the build process Thomas Petazzoni
2014-10-08 20:49 ` Yann E. MORIN
2014-10-08 20:23 ` Yann E. MORIN [this message]
2014-10-08 20:25 ` [Buildroot] [PATCH 1/2] docs/manual: slightly improve faq entry about compiler on target Thomas Petazzoni
2014-10-08 20:50 ` Yann E. MORIN
2014-10-12 15:27 ` 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=20141008202313.GC4718@free.fr \
--to=yann.morin.1998@free.fr \
--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.