ref-manual, dev-manual, adt-manual, yocto-project-qs: scrub eglibc

Scrubbed out the occurrences of eglibc and replaced them with
glibc.

Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 868ceda79b1c738349e512e523c850b24f9232ca)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2015-01-21 11:21:30 -08:00 committed by Richard Purdie
parent 9a47967a18
commit db874ed595
9 changed files with 34 additions and 37 deletions

View File

@ -276,7 +276,7 @@
target, go into the <filename>x86_64</filename> target, go into the <filename>x86_64</filename>
folder and download the following installer: folder and download the following installer:
<literallayout class='monospaced'> <literallayout class='monospaced'>
poky-eglibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh poky-glibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh
</literallayout></para></listitem> </literallayout></para></listitem>
<listitem><para>Build your own toolchain installer. <listitem><para>Build your own toolchain installer.
For cases where you cannot use an installer For cases where you cannot use an installer
@ -296,7 +296,7 @@
The example assumes the toolchain installer is located The example assumes the toolchain installer is located
in <filename>~/Downloads/</filename>. in <filename>~/Downloads/</filename>.
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ ~/Downloads/poky-eglibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh $ ~/Downloads/poky-glibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh
</literallayout> </literallayout>
The first thing the installer prompts you for is the The first thing the installer prompts you for is the
directory into which you want to install the toolchain. directory into which you want to install the toolchain.
@ -656,10 +656,10 @@
<ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'><filename>IMAGE_INSTALL</filename></ulink> <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'><filename>IMAGE_INSTALL</filename></ulink>
variable inside your <filename>local.conf</filename> file to variable inside your <filename>local.conf</filename> file to
install the appropriate library packages. install the appropriate library packages.
Following is an example using <filename>eglibc</filename> static Following is an example using <filename>glibc</filename> static
development libraries: development libraries:
<literallayout class='monospaced'> <literallayout class='monospaced'>
IMAGE_INSTALL_append = " eglibc-staticdev" IMAGE_INSTALL_append = " glibc-staticdev"
</literallayout> </literallayout>
</note> </note>
</para> </para>

View File

@ -1088,7 +1088,7 @@
<filename><ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'>IMAGE_INSTALL</ulink></filename> <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'>IMAGE_INSTALL</ulink></filename>
variable. variable.
You must use the OpenEmbedded notation and not the Debian notation for the names You must use the OpenEmbedded notation and not the Debian notation for the names
(e.g. <filename>eglibc-dev</filename> instead of <filename>libc6-dev</filename>). (e.g. <filename>glibc-dev</filename> instead of <filename>libc6-dev</filename>).
</para> </para>
<para> <para>
@ -3060,7 +3060,7 @@
<note> <note>
Although well within the capabilities of the Yocto Project, Although well within the capabilities of the Yocto Project,
adding a totally new architecture might require adding a totally new architecture might require
changes to <filename>gcc/eglibc</filename> and to the site changes to <filename>gcc/glibc</filename> and to the site
information, which is beyond the scope of this manual. information, which is beyond the scope of this manual.
</note> </note>
</para> </para>
@ -5943,10 +5943,10 @@
described here combined with experimentation and iteration. described here combined with experimentation and iteration.
Here are a couple of areas to experiment with: Here are a couple of areas to experiment with:
<itemizedlist> <itemizedlist>
<listitem><para><filename>eglibc</filename>: <listitem><para><filename>glibc</filename>:
In general, follow this process: In general, follow this process:
<orderedlist> <orderedlist>
<listitem><para>Remove <filename>eglibc</filename> <listitem><para>Remove <filename>glibc</filename>
features from features from
<ulink url='&YOCTO_DOCS_REF_URL;#var-DISTRO_FEATURES'><filename>DISTRO_FEATURES</filename></ulink> <ulink url='&YOCTO_DOCS_REF_URL;#var-DISTRO_FEATURES'><filename>DISTRO_FEATURES</filename></ulink>
that you think you do not need.</para></listitem> that you think you do not need.</para></listitem>
@ -5960,7 +5960,7 @@
support wide character support as is done for support wide character support as is done for
<filename>ncurses</filename>. <filename>ncurses</filename>.
Or, if support for those characters is needed, Or, if support for those characters is needed,
determine what <filename>eglibc</filename> determine what <filename>glibc</filename>
features provide the support and restore the features provide the support and restore the
configuration. configuration.
</para></listitem> </para></listitem>
@ -5969,7 +5969,7 @@
</orderedlist></para></listitem> </orderedlist></para></listitem>
<listitem><para><filename>busybox</filename>: <listitem><para><filename>busybox</filename>:
For BusyBox, use a process similar as described for For BusyBox, use a process similar as described for
<filename>eglibc</filename>. <filename>glibc</filename>.
A difference is you will need to boot the resulting A difference is you will need to boot the resulting
system to see if you are able to do everything you system to see if you are able to do everything you
expect from the running system. expect from the running system.

View File

@ -398,7 +398,7 @@
Execute the installation script. Execute the installation script.
Here is an example: Here is an example:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ sh poky-eglibc-x86_64-buildtools-tarball-x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh $ sh poky-glibc-x86_64-buildtools-tarball-x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh
</literallayout> </literallayout>
During execution, a prompt appears that allows you to During execution, a prompt appears that allows you to
choose the installation directory. choose the installation directory.
@ -484,7 +484,7 @@
to install the tools. to install the tools.
Here is an example: Here is an example:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ sh poky-eglibc-x86_64-buildtools-tarball-x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh $ sh poky-glibc-x86_64-buildtools-tarball-x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh
</literallayout> </literallayout>
During execution, a prompt appears that allows you to During execution, a prompt appears that allows you to
choose the installation directory. choose the installation directory.

View File

@ -169,7 +169,7 @@
<filename>packagegroup-core-x11-sato</filename>, <filename>packagegroup-core-x11-sato</filename>,
which in turn leads to recipes like <filename>matchbox-terminal</filename>, which in turn leads to recipes like <filename>matchbox-terminal</filename>,
<filename>pcmanfm</filename> and <filename>gthumb</filename>. <filename>pcmanfm</filename> and <filename>gthumb</filename>.
These recipes in turn depend on <filename>eglibc</filename> and the toolchain. These recipes in turn depend on <filename>glibc</filename> and the toolchain.
</para> </para>
<para> <para>

View File

@ -580,8 +580,8 @@
<para> <para>
The <filename>debian</filename> class renames output packages so that The <filename>debian</filename> class renames output packages so that
they follow the Debian naming policy (i.e. <filename>eglibc</filename> they follow the Debian naming policy (i.e. <filename>glibc</filename>
becomes <filename>libc6</filename> and <filename>eglibc-devel</filename> becomes <filename>libc6</filename> and <filename>glibc-devel</filename>
becomes <filename>libc6-dev</filename>.) becomes <filename>libc6-dev</filename>.)
Renaming includes the library name and version as part of the package Renaming includes the library name and version as part of the package
name. name.
@ -2808,7 +2808,7 @@
file. file.
Here is an example: Here is an example:
<literallayout class='monospaced'> <literallayout class='monospaced'>
RM_WORK_EXCLUDE += "busybox eglibc" RM_WORK_EXCLUDE += "busybox glibc"
</literallayout> </literallayout>
</para> </para>
</section> </section>

View File

@ -691,7 +691,7 @@
<para> <para>
This directory receives package licensing information. This directory receives package licensing information.
For example, the directory contains sub-directories for <filename>bash</filename>, For example, the directory contains sub-directories for <filename>bash</filename>,
<filename>busybox</filename>, and <filename>eglibc</filename> (among others) that in turn <filename>busybox</filename>, and <filename>glibc</filename> (among others) that in turn
contain appropriate <filename>COPYING</filename> license files with other licensing information. contain appropriate <filename>COPYING</filename> license files with other licensing information.
For information on licensing, see the For information on licensing, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#maintaining-open-source-license-compliance-during-your-products-lifecycle'>Maintaining Open Source License Compliance During Your Product's Lifecycle</ulink>" "<ulink url='&YOCTO_DOCS_DEV_URL;#maintaining-open-source-license-compliance-during-your-products-lifecycle'>Maintaining Open Source License Compliance During Your Product's Lifecycle</ulink>"

View File

@ -2891,7 +2891,7 @@
</info> </info>
<glossdef> <glossdef>
<para>Variable that controls which locales for <para>Variable that controls which locales for
<filename>eglibc</filename> are generated during the <filename>glibc</filename> are generated during the
build (useful if the target device has 64Mbytes build (useful if the target device has 64Mbytes
of RAM or less).</para> of RAM or less).</para>
</glossdef> </glossdef>
@ -7117,7 +7117,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
Declares the oldest version of the Linux kernel that the Declares the oldest version of the Linux kernel that the
produced binaries must support. produced binaries must support.
This variable is passed into the build of the Embedded This variable is passed into the build of the Embedded
GNU C Library (<filename>eglibc</filename>). GNU C Library (<filename>glibc</filename>).
</para> </para>
<para> <para>
@ -7811,7 +7811,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
</info> </info>
<glossdef> <glossdef>
<para>Specifies the recipe or package name and includes all version and revision <para>Specifies the recipe or package name and includes all version and revision
numbers (i.e. <filename>eglibc-2.13-r20+svnr15508/</filename> and numbers (i.e. <filename>glibc-2.13-r20+svnr15508/</filename> and
<filename>bash-4.2-r1/</filename>). <filename>bash-4.2-r1/</filename>).
This variable is comprised of the following: This variable is comprised of the following:
<literallayout class='monospaced'> <literallayout class='monospaced'>
@ -10731,7 +10731,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
</info> </info>
<glossdef> <glossdef>
<para>Specifies the target's operating system. <para>Specifies the target's operating system.
The variable can be set to "linux" for <filename>eglibc</filename>-based systems and The variable can be set to "linux" for <filename>glibc</filename>-based systems and
to "linux-uclibc" for <filename>uclibc</filename>. to "linux-uclibc" for <filename>uclibc</filename>.
For ARM/EABI targets, there are also "linux-gnueabi" and For ARM/EABI targets, there are also "linux-gnueabi" and
"linux-uclibc-gnueabi" values possible.</para> "linux-uclibc-gnueabi" values possible.</para>
@ -10817,7 +10817,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
supported. supported.
</para> </para>
<para> <para>
You can select "eglibc" or "uclibc". You can select "glibc" or "uclibc".
<note> <note>
This release of the Yocto Project does not support the This release of the Yocto Project does not support the
<filename>glibc</filename> implementation of <filename>libc</filename>. <filename>glibc</filename> implementation of <filename>libc</filename>.
@ -10882,7 +10882,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
<link linkend='var-TCLIBC'><filename>TCLIBC</filename></link>, <link linkend='var-TCLIBC'><filename>TCLIBC</filename></link>,
which controls the variant of the GNU standard C library which controls the variant of the GNU standard C library
(<filename>libc</filename>) used during the build process: (<filename>libc</filename>) used during the build process:
<filename>eglibc</filename> or <filename>uclibc</filename>. <filename>glibc</filename> or <filename>uclibc</filename>.
</para> </para>
</glossdef> </glossdef>
</glossentry> </glossentry>

View File

@ -107,11 +107,8 @@
<para> <para>
BitBake also tries to execute any dependent tasks first. BitBake also tries to execute any dependent tasks first.
So for example, before building <filename>matchbox-desktop</filename>, BitBake So for example, before building <filename>matchbox-desktop</filename>, BitBake
would build a cross compiler and <filename>eglibc</filename> if they had not already would build a cross compiler and <filename>glibc</filename> if they had not already
been built. been built.
<note>This release of the Yocto Project does not support the <filename>glibc</filename>
GNU version of the Unix standard C library. By default, the OpenEmbedded build system
builds with <filename>eglibc</filename>.</note>
</para> </para>
<para> <para>
@ -228,7 +225,7 @@
The chain of events that occurs when <filename>gcc-cross</filename> is The chain of events that occurs when <filename>gcc-cross</filename> is
bootstrapped is as follows: bootstrapped is as follows:
<literallayout class='monospaced'> <literallayout class='monospaced'>
gcc -> binutils-cross -> gcc-cross-initial -> linux-libc-headers -> eglibc-initial -> eglibc -> gcc-cross -> gcc-runtime gcc -> binutils-cross -> gcc-cross-initial -> linux-libc-headers -> glibc-initial -> glibc -> gcc-cross -> gcc-runtime
</literallayout> </literallayout>
<itemizedlist> <itemizedlist>
<listitem><para><filename>gcc</filename>: <listitem><para><filename>gcc</filename>:
@ -251,9 +248,9 @@
<listitem><para><filename>linux-libc-headers</filename>: <listitem><para><filename>linux-libc-headers</filename>:
Headers needed for the cross-compiler. Headers needed for the cross-compiler.
</para></listitem> </para></listitem>
<listitem><para><filename>eglibc-initial</filename>: <listitem><para><filename>glibc-initial</filename>:
An initial version of the Embedded GLIBC needed to bootstrap An initial version of the Embedded GLIBC needed to bootstrap
<filename>eglibc</filename>. <filename>glibc</filename>.
</para></listitem> </para></listitem>
<listitem><para><filename>gcc-cross</filename>: <listitem><para><filename>gcc-cross</filename>:
The final stage of the bootstrap process for the The final stage of the bootstrap process for the
@ -305,7 +302,7 @@
Here is the bootstrap process for the relocatable toolchain: Here is the bootstrap process for the relocatable toolchain:
<literallayout class='monospaced'> <literallayout class='monospaced'>
gcc -> binutils-crosssdk -> gcc-crosssdk-initial -> linux-libc-headers -> gcc -> binutils-crosssdk -> gcc-crosssdk-initial -> linux-libc-headers ->
eglibc-initial -> nativesdk-eglibc -> gcc-crosssdk -> gcc-cross-canadian glibc-initial -> nativesdk-glibc -> gcc-crosssdk -> gcc-cross-canadian
</literallayout> </literallayout>
<itemizedlist> <itemizedlist>
<listitem><para><filename>gcc</filename>: <listitem><para><filename>gcc</filename>:
@ -328,11 +325,11 @@
<listitem><para><filename>linux-libc-headers</filename>: <listitem><para><filename>linux-libc-headers</filename>:
Headers needed for the cross-compiler. Headers needed for the cross-compiler.
</para></listitem> </para></listitem>
<listitem><para><filename>eglibc-initial</filename>: <listitem><para><filename>glibc-initial</filename>:
An initial version of the Embedded GLIBC needed to bootstrap An initial version of the Embedded GLIBC needed to bootstrap
<filename>nativesdk-eglibc</filename>. <filename>nativesdk-glibc</filename>.
</para></listitem> </para></listitem>
<listitem><para><filename>nativesdk-eglibc</filename>: <listitem><para><filename>nativesdk-glibc</filename>:
The Embedded GLIBC needed to bootstrap the The Embedded GLIBC needed to bootstrap the
<filename>gcc-crosssdk</filename>. <filename>gcc-crosssdk</filename>.
</para></listitem> </para></listitem>

View File

@ -627,7 +627,7 @@
</para> </para>
<literallayout class='monospaced'> <literallayout class='monospaced'>
poky-eglibc-<replaceable>host_system</replaceable>-<replaceable>image_type</replaceable>-<replaceable>arch</replaceable>-toolchain-<replaceable>release_version</replaceable>.sh poky-glibc-<replaceable>host_system</replaceable>-<replaceable>image_type</replaceable>-<replaceable>arch</replaceable>-toolchain-<replaceable>release_version</replaceable>.sh
Where: Where:
<replaceable>host_system</replaceable> is a string representing your development system: <replaceable>host_system</replaceable> is a string representing your development system:
@ -656,7 +656,7 @@
development host system and a i586-tuned target architecture development host system and a i586-tuned target architecture
based off the SDK for <filename>core-image-sato</filename>: based off the SDK for <filename>core-image-sato</filename>:
<literallayout class='monospaced'> <literallayout class='monospaced'>
poky-eglibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh poky-glibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh
</literallayout> </literallayout>
</para> </para>
@ -685,7 +685,7 @@
<para> <para>
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ ~/Downloads/poky-eglibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh $ ~/Downloads/poky-glibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh
</literallayout> </literallayout>
</para> </para>