From fba1478dba9095f0007730e844793ad38d9b5af2 Mon Sep 17 00:00:00 2001 From: Manuel Canales Esparcia Date: Mon, 20 Dec 2004 17:23:16 +0000 Subject: Removed text in chapter 05 - second round. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4433 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter05/glibc.xml | 133 ++-------------------------------------------------- 1 file changed, 5 insertions(+), 128 deletions(-) (limited to 'chapter05/glibc.xml') diff --git a/chapter05/glibc.xml b/chapter05/glibc.xml index 3b7ac093a..b256792f1 100644 --- a/chapter05/glibc.xml +++ b/chapter05/glibc.xml @@ -12,7 +12,6 @@ tools -<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/glibc.xml" xpointer="xpointer(/sect1/sect2[1]/para[1])"/> <segmentedlist> <segtitle>&buildtime;</segtitle> @@ -20,25 +19,11 @@ <seglistitem><seg>11.8 SBU</seg><seg>800 MB</seg></seglistitem> </segmentedlist> -<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/glibc.xml" xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/> - </sect2> <sect2 role="installation"> <title>Installation of Glibc -This package is known to behave badly when you change 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 un-setting them when building Glibc. - -Basically, compiling Glibc in any other way than the book suggests -is putting the stability of your system at risk. - -The Glibc documentation recommends building Glibc outside of the source -directory in a dedicated build directory: - mkdir ../glibc-build cd ../glibc-build @@ -49,104 +34,15 @@ cd ../glibc-build --enable-kernel=2.6.0 --with-binutils=/tools/bin \ --without-gd --without-cvs --with-headers=/tools/include -The meaning of the configure options: - - - ---disable-profile -This builds the -libraries without profiling information. Omit this option if you plan to do -profiling on the temporary tools. - - - ---enable-add-ons -This tells Glibc to use the add-on' that it can use like NPTL -as its threading library. - - - ---enable-kernel=2.6.0 -This tells Glibc to compile the library for support of -linux 2.6.x kernels. - - - - ---with-binutils=/tools/bin -Strictly speaking this switch is not required. But it does ensure -nothing can go wrong with regard to what Binutils programs get used during the -Glibc build. - - - ---without-gd -This prevents the build of the memusagestat -program, which strangely enough insists on linking against the host's libraries -(libgd, libpng, libz, and so forth). - - - ---without-cvs -This is meant to prevent -the Makefiles from attempting automatic CVS checkouts when using a CVS -snapshot. But it's not actually needed these days. We use it because it -suppresses an annoying but harmless warning about a missing -autoconf program. - - - ---with-headers=/tools/include -This forces glibc to use the linux-libc-headers installed -in /tools/include, rather than those on the host, which may be too old to -support needed functionality. - - - - -During this stage you might see the following warning: - -
configure: WARNING: -*** These auxiliary programs are missing or incompatible versions: msgfmt -*** some features will be disabled. -*** Check the INSTALL file for required versions.
- -The missing or incompatible msgfmt program is -generally harmless, but it's believed it can sometimes cause problems when -running the test suite. - Compile the package: make -Compilation is now complete. As mentioned earlier, running the test suites -for the temporary tools installed in this chapter is not mandatory. If you want -to run the Glibc test suite though, the following command will do so: - make check For a discussion of test failures that are of particular importance, please see . -In this chapter, some tests can be adversely affected by existing tools or -environmental issues on the host system. In short, don't worry too much if you -see Glibc test suite failures in this chapter. The Glibc in - 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 math tests, -for example). - -When experiencing a failure, make a note of it, then continue by reissuing -the make check. The test suite should pick up where it left -off and continue. You can circumvent this stop-start sequence by issuing a -make -k check. If you do that though, be sure to log the -output so that you can later peruse the log file and examine the total number of -failures. - -Though it is a harmless message, the install stage of Glibc will at the -end complain about the absence of /tools/etc/ld.so.conf. -Prevent this confusing little warning with: - mkdir /tools/etc touch /tools/etc/ld.so.conf @@ -154,30 +50,15 @@ touch /tools/etc/ld.so.conf make install -Different countries and cultures have varying conventions for how to -communicate. These conventions range from very simple ones, such as the format -for representing dates and times, to very complex ones, such as the language -spoken. The internationalization of GNU programs works by means -of locales. - -If you are not running the test suites here in this chapter as per -our recommendation, there is little point in installing the locales now. We'll -be installing the locales in the next chapter. - -If you still want to install the Glibc locales anyway, the following -command will do so: +To install the Glibc locales, use the following +command: make localedata/install-locales An alternative to running the previous command is to install only those -locales which you need or want. This can be achieved by using the -localedef command. Information on this can be found in -the INSTALL file in the Glibc source. However, there are -a number of locales that are essential for the tests of future packages to -pass, in particular, the libstdc++ tests from GCC. The -following instructions, instead of the install-locales target above, will -install the minimum set of locales necessary for the tests to run -successfully: +locales which you need or want. The following instructions, instead of the +install-locales target above, will install the minimum set of locales necessary +for the tests to run successfully: mkdir -p /tools/lib/locale localedef -i de_DE -f ISO-8859-1 de_DE @@ -194,8 +75,4 @@ localedef -i ja_JP -f EUC-JP ja_JP - -<para>The details on this package are found in <xref linkend="contents-glibc"/>.</para> -</sect2> - </sect1> -- cgit v1.2.3-54-g00ecf