Several manuals and areas were still referring to 'glibc' as the
GNU version of the Unix statndrd C library. We do not support this
any longer and now use 'eglibc' to build with. Notable changes were
in the required packages area of the QS manual. I also added a
bit in the reference guide saying how this release does not use
'glibc' to build with but rather 'eglibc'.
(From yocto-docs rev:
c2c58914996d747c510706d78ecfd8f41c5e694d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is important to use the correct names of packages in the
<filename><link linkend='var-IMAGE_INSTALL'>IMAGE_INSTALL</link></filename> variable.
You must use the OpenEmbedded notation and not the Debian notation for the names
- (e.g. <filename>glibc-dev</filename> instead of <filename>libc6-dev</filename>).
+ (e.g. <filename>eglibc-dev</filename> instead of <filename>libc6-dev</filename>).
</para>
<para>
The information covers adding machines similar to those the Yocto Project already supports.
Although well within the capabilities of the Yocto Project, adding a totally new architecture
might require
- changes to <filename>gcc/glibc</filename> and to the site information, which is
+ changes to <filename>gcc/eglibc</filename> and to the site information, which is
beyond the scope of this manual.
</para>
<filename>task-base.bb</filename>,
which in turn leads to packages like <filename>Contacts</filename>,
<filename>Dates</filename> and <filename>BusyBox</filename>.
- These packages in turn depend on glibc and the toolchain.
+ These packages in turn depend on <filename>eglibc</filename> and the toolchain.
</para>
<para>
<para>
This class renames packages so that they follow the Debian naming
- policy (i.e. <filename>glibc</filename> becomes <filename>libc6</filename>
- and <filename>glibc-devel</filename> becomes <filename>libc6-dev</filename>.
+ policy (i.e. <filename>eglibc</filename> becomes <filename>libc6</filename>
+ and <filename>eglibc-devel</filename> becomes <filename>libc6-dev</filename>.
</para>
</section>
still make the correct values available.
The <filename><link linkend='structure-meta-site'>meta/site directory</link></filename>
contains test results sorted into different categories such as architecture, endianness, and
- the libc used.
+ the <filename>libc</filename> used.
Site information provides a list of files containing data relevant to
the current build in the
<filename><link linkend='var-CONFIG_SITE'>CONFIG_SITE</link></filename> variable
<glossentry id='var-ENABLE_BINARY_LOCALE_GENERATION'><glossterm>ENABLE_BINARY_LOCALE_GENERATION</glossterm>
<glossdef>
- <para>Variable that controls which locales for <filename>glibc</filename> are
+ <para>Variable that controls which locales for <filename>eglibc</filename> are
to be generated during the build (useful if the target device has 64Mbytes
of RAM or less).</para>
</glossdef>
<glossentry id='var-POKYLIBC'><glossterm>POKYLIBC</glossterm>
<glossdef>
<para>The <filename>libc</filename> implementation selector.
- You can select <filename>glibc</filename>, <filename>eglibc</filename>,
- or <filename>uclibc</filename>.</para>
+ You can select <filename>eglibc</filename> or <filename>uclibc</filename>.
+ <note>This release of the Yocto Project does not support the
+ <filename>glibc</filename> implementation of <filename>libc</filename>.</note>
+ </para>
</glossdef>
</glossentry>
<glossentry id='var-TARGET_OS'><glossterm>TARGET_OS</glossterm>
<glossdef>
<para>Specifies the target's operating system.
- The variable can be set to "linux" for <filename>glibc</filename>-based systems and
- "linux-uclibc" for <filename>uClibc</filename>.
+ The variable can be set to "linux" for <filename>eglibc</filename>-based systems and
+ to "linux-uclibc" for <filename>uclibc</filename>.
For ARM/EABI targets, there are also "linux-gnueabi" and
"linux-uclibc-gnueabi" values possible.</para>
</glossdef>
<para>
BitBake also tries to execute any dependent tasks first.
So for example, before building <filename>matchbox-desktop</filename>, BitBake
- would build a cross compiler and <filename>glibc</filename> if they had not already
+ would build a cross compiler and <filename>eglibc</filename> if they had not already
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 Yocto Project builds with
+ <filename>eglibc</filename>.</note>
</para>
<para>
$ sudo yum install python m4 make wget curl ftp hg tar bzip2 gzip \
unzip python-psyco perl texinfo texi2html diffstat openjade \
docbook-style-dsssl sed docbook-style-xsl docbook-dtds \
- docbook-utils sed bc glibc-devel ccache pcre pcre-devel quilt \
+ docbook-utils sed bc eglibc-devel ccache pcre pcre-devel quilt \
groff linuxdoc-tools patch linuxdoc-tools cmake help2man \
perl-ExtUtils-MakeMaker tcl-devel gettext chrpath ncurses apr \
SDL-devel mesa-libGL-devel mesa-libGLU-devel gnome-doc-utils \