diff options
Diffstat (limited to 'chapter05/glibc.xml')
| -rw-r--r-- | chapter05/glibc.xml | 51 |
1 files changed, 25 insertions, 26 deletions
diff --git a/chapter05/glibc.xml b/chapter05/glibc.xml index 4e8ab7b66..9eda176a6 100644 --- a/chapter05/glibc.xml +++ b/chapter05/glibc.xml @@ -13,11 +13,11 @@ <sect2> <title>Installation of Glibc</title> -<para>This package is known to behave badly when you have changed its -default optimization flags (including the -march and -mcpu options). -Therefore, if you have defined any environment variables that override -default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting -them when building Glibc.</para> +<para>This package is known to behave badly when you change its default +optimization flags (including the <emphasis>-march</emphasis> and +<emphasis>-mcpu</emphasis> options). Therefore, if you have defined any +environment variables that override default optimizations, such as CFLAGS and +CXXFLAGS, we recommend unsetting them when building Glibc.</para> <para>Basically, compiling Glibc in any other way than the book suggests is putting the stability of your system at risk.</para> @@ -40,7 +40,7 @@ cd ../glibc-build</userinput></screen> <itemizedlist> <listitem><para><userinput>--disable-profile</userinput>: This disables the building of the libraries with profiling information. Omit this option if you -plan to do profiling.</para></listitem> +plan to do profiling on the temporary tools.</para></listitem> <listitem><para><userinput>--enable-add-ons=linuxthreads</userinput>: This tells Glibc to use the Linuxthreads add-on as its threading @@ -71,7 +71,7 @@ suppresses an annoying but harmless warning about a missing *** some features will be disabled. *** Check the INSTALL file for required versions.</screen></blockquote> -<para>The missing or incompatible <filename>msgfmt</filename> program is +<para>The missing or incompatible <command>msgfmt</command> program is generally harmless, but it's believed it can sometimes cause problems when running the test suite.</para> @@ -79,7 +79,7 @@ running the test suite.</para> <screen><userinput>make</userinput></screen> -<para>Compilation is now complete. As discussed earlier, we don't recommend +<para>Compilation is now complete. As mentioned earlier, we don't recommend running the test suites for the temporary system here in this chapter. If you still want to run the Glibc test suite anyway, the following command will do so:</para> @@ -90,10 +90,10 @@ so:</para> system, in particular the kernel. Additionally, here in this chapter some tests can be adversely affected by existing tools or environmental issues on the host system. Of course, these won't be a problem when we run the Glibc test suite -inside the chroot environment of <xref linkend="chapter-building-system"/>. In general, the -Glibc test suite is always expected to pass. However, as mentioned above, some -failures are unavoidable in certain circumstances. Here is a list of the most -common issues we are aware of:</para> +inside the chroot environment of <xref linkend="chapter-building-system"/>. In +general, the Glibc test suite is always expected to pass. However, as mentioned +above, in certain circumstances some failures are unavoidable. Here is a list +of the most common issues we are aware of:</para> <itemizedlist> <listitem><para>The <emphasis>math</emphasis> tests sometimes fail when running @@ -117,20 +117,19 @@ fail due to test timeouts being exceeded.</para></listitem> </itemizedlist> <para>In summary, don't worry too much if you see Glibc test suite failures -here in this chapter. The Glibc in <xref linkend="chapter-building-system"/> is the one we'll -ultimately end up using so that is the one we would really like to see pass. -But please keep in mind, even in <xref linkend="chapter-building-system"/> some failures -could still occur -- the <emphasis>math</emphasis> -tests for example. When experiencing a failure, make a note of it, then -continue by reissuing the <command>make check</command>. The test suite -should pick up where it left off and continue on. You can circumvent this -stop-start sequence by issuing a <command>make -k check</command>. But if -you do that, be sure to log the output so that you can later peruse the log -file and examine the total number of failures.</para> - -<para>Though it is a harmless message, the install stage of Glibc will -complain about the absence of <filename>/tools/etc/ld.so.conf</filename>. -Fix this annoying little warning with:</para> +here in this chapter. The Glibc in <xref linkend="chapter-building-system"/> is +the one we'll ultimately end up using, so that is the one we would really like +to see pass the tests (but even there some failures could still occur -- the +<emphasis>math</emphasis> tests, for example). When experiencing a failure, +make a note of it, then continue by reissuing the <command>make +check</command>. The test suite should pick up where it left off and continue. +You can circumvent this stop-start sequence by issuing a <command>make -k +check</command>. But if you do that, be sure to log the output so that you can +later peruse the log file and examine the total number of failures.</para> + +<para>Though it is a harmless message, the install stage of Glibc will at the +end complain about the absence of <filename>/tools/etc/ld.so.conf</filename>. +Prevent this confusing little warning with:</para> <screen><userinput>mkdir /tools/etc touch /tools/etc/ld.so.conf</userinput></screen> |