From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 07/13] docs/manual: update informations about C library in internal backend
Date: Sun, 23 Feb 2014 17:21:20 +0100 [thread overview]
Message-ID: <20140223162120.GB32759@free.fr> (raw)
In-Reply-To: <1393167879-16637-8-git-send-email-thomas.petazzoni@free-electrons.com>
Thomas, All,
On 2014-02-23 16:04 +0100, Thomas Petazzoni spake thusly:
> Now that we have eglibc and glibc support in the internal backend, and
> no longer marked as experimental, a little bit of rewording is
> needed. It is no longer necessary to indicate that uClibc was
> historically supported as the only C library, and that the glibc
> support is experimental. We also update the rest of the description to
> be less uClibc specific.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> docs/manual/configure.txt | 30 +++++++++++-------------------
> 1 file changed, 11 insertions(+), 19 deletions(-)
>
> diff --git a/docs/manual/configure.txt b/docs/manual/configure.txt
> index 89df3d9..b566e8a 100644
> --- a/docs/manual/configure.txt
> +++ b/docs/manual/configure.txt
> @@ -68,12 +68,10 @@ The _internal toolchain backend_ is the backend where Buildroot builds
> by itself a cross-compilation toolchain, before building the userspace
> applications and libraries for your target embedded system.
>
> -This backend is the historical backend of Buildroot, and has been
> -limited for a long time to the usage of the
> -http://www.uclibc.org[uClibc C library]. Support for the _eglibc_ C
> -library has been added in 2013 and is at this point considered
> -experimental. See the _External toolchain backend_ for another
> -solution to use _glibc_ or _eglibc_.
> +This backend supports several C libraries:
> +http://www.uclibc.org[uClibc], the
s/the// since you don't do it for the other two.
> +http://www.gnu.org/software/libc/libc.html[glibc] and
> +http://www.eglibc.org[eglibc].
>
> Once you have selected this backend, a number of options appear. The
> most important ones allow to:
> @@ -96,18 +94,7 @@ most important ones allow to:
> the C library might be using interfaces that are not provided by
> your Linux kernel.
Unrelated to your patch, but what about:
[...] the C library might be using interfaces, or exposing thos
interfaces to applications, that are not provided by the running
Linux kernel.
> - * Change the version and the configuration of the uClibc C library
> - (if uClibc is selected). The default options are usually
> - fine. However, if you really need to specifically customize the
> - configuration of your uClibc C library, you can pass a specific
> - configuration file here. Or alternatively, you can run the +make
> - uclibc-menuconfig+ command to get access to uClibc's configuration
> - interface. Note that all packages in Buildroot are tested against
> - the default uClibc configuration bundled in Buildroot: if you
> - deviate from this configuration by removing features from uClibc,
> - some packages may no longer build.
> -
> - * Change the version of the GCC compiler and binutils.
> + * Change the version of the GCC compiler, binutils and the C library.
>
> * Select a number of toolchain options (uClibc only): whether the
> toolchain should have largefile support (i.e support for files
> @@ -118,7 +105,12 @@ most important ones allow to:
> libraries visible in Buildroot menus will change: many applications
> and libraries require certain toolchain options to be enabled. Most
> packages show a comment when a certain toolchain option is required
> - to be able to enable those packages.
> + to be able to enable those packages. If needed, you can further
> + refine the uClibc configuration by running +make
> + uclibc-menuconfig+. Note however that all packages in Buildroot are
> + tested against the default uClibc configuration bundled in
> + Buildroot: if you deviate from this configuration by removing
> + features from uClibc, some packages may no longer build.
>
> It is worth noting that whenever one of those options is modified,
> then the entire toolchain and system must be rebuilt. See
Otherwise, looks good.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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-02-23 16:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 15:04 [Buildroot] [PATCH 00/13] Documentation updates and improvements Thomas Petazzoni
2014-02-23 15:04 ` [Buildroot] [PATCH 01/13] docs/manual: toolchain packages no longer use custom makefiles Thomas Petazzoni
2014-02-23 15:16 ` Yann E. MORIN
2014-02-23 15:04 ` [Buildroot] [PATCH 02/13] docs/manual: rephrase part about rebuilding packages Thomas Petazzoni
2014-02-23 15:19 ` Yann E. MORIN
2014-02-23 15:04 ` [Buildroot] [PATCH 03/13] docs/manual: rephrase and expand part on when a full rebuild is necessary Thomas Petazzoni
2014-02-23 15:24 ` Yann E. MORIN
2014-02-23 15:04 ` [Buildroot] [PATCH 04/13] docs/manual: reference Python and Lua infras from the list of package infrastructures Thomas Petazzoni
2014-02-23 15:29 ` Yann E. MORIN
2014-02-23 15:37 ` Thomas Petazzoni
2014-02-23 15:04 ` [Buildroot] [PATCH 05/13] docs/manual: add section about dependency graphs Thomas Petazzoni
2014-02-23 15:32 ` Yann E. MORIN
2014-02-23 15:04 ` [Buildroot] [PATCH 06/13] docs/manual: add section about build time graphing Thomas Petazzoni
2014-02-23 15:35 ` Yann E. MORIN
2014-02-23 15:04 ` [Buildroot] [PATCH 07/13] docs/manual: update informations about C library in internal backend Thomas Petazzoni
2014-02-23 16:21 ` Yann E. MORIN [this message]
2014-02-23 15:04 ` [Buildroot] [PATCH 08/13] docs/manual: update external toolchain examples Thomas Petazzoni
2014-02-23 15:39 ` Yann E. MORIN
2014-02-23 15:04 ` [Buildroot] [PATCH 09/13] docs/manual: mention that custom toolchains is also useful for BR toolchains Thomas Petazzoni
2014-02-23 15:48 ` Yann E. MORIN
2014-02-23 15:04 ` [Buildroot] [PATCH 10/13] docs/manual: rephrase paragraph about unsupported external toolchains Thomas Petazzoni
2014-02-23 15:04 ` [Buildroot] [PATCH 11/13] docs/manual: refresh informations about *-menuconfig targets Thomas Petazzoni
2014-02-23 15:53 ` Yann E. MORIN
2014-02-23 15:04 ` [Buildroot] [PATCH 12/13] docs/manual: document the usage of <pkg>_OVERRIDE_SRCDIR Thomas Petazzoni
2014-02-23 16:29 ` Yann E. MORIN
2014-02-23 21:29 ` Peter Korsgaard
2014-02-23 21:33 ` Yann E. MORIN
2014-02-23 15:04 ` [Buildroot] [PATCH 13/13] docs/manual: mention the per-package graph-depends target Thomas Petazzoni
2014-02-23 16:06 ` Yann E. MORIN
2014-02-23 21:30 ` [Buildroot] [PATCH 00/13] Documentation updates and improvements 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=20140223162120.GB32759@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox