From 92474b451445f3a1822c5ce6353ff91ff9d65e2d Mon Sep 17 00:00:00 2001 From: Manuel Canales Esparcia Date: Wed, 1 Feb 2006 20:41:29 +0000 Subject: Indenting chapter 6, part 2. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7324 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter06/binutils.xml | 533 +++++++++++++++++++++++++++---------------------- 1 file changed, 296 insertions(+), 237 deletions(-) (limited to 'chapter06/binutils.xml') diff --git a/chapter06/binutils.xml b/chapter06/binutils.xml index c5f7926b7..59a0f0ca4 100644 --- a/chapter06/binutils.xml +++ b/chapter06/binutils.xml @@ -1,277 +1,336 @@ - %general-entities; ]> + -Binutils-&binutils-version; - + + + Binutils-&binutils-version; + + + Binutils + + + + -<indexterm zone="ch-system-binutils"><primary sortas="a-Binutils">Binutils</primary></indexterm> + <para>The Binutils package contains a linker, an assembler, and other + tools for handling object files.</para> -<sect2 role="package"><title/> -<para>The Binutils package contains a linker, an assembler, and other tools for -handling object files.</para> + <segmentedlist> + <segtitle>&buildtime;</segtitle> + <segtitle>&diskspace;</segtitle> -<segmentedlist> -<segtitle>&buildtime;</segtitle> -<segtitle>&diskspace;</segtitle> -<seglistitem><seg>1.3 SBU</seg><seg>158 MB</seg></seglistitem> -</segmentedlist> + <seglistitem> + <seg>1.3 SBU</seg> + <seg>158 MB</seg> + </seglistitem> + </segmentedlist> -<segmentedlist> -<segtitle>&dependencies;</segtitle> -<seglistitem><seg>Bash, Coreutils, Diffutils, GCC, Gettext, -Glibc, Grep, M4, Make, Perl, Sed, and Texinfo</seg></seglistitem> -</segmentedlist> -</sect2> + <segmentedlist> + <segtitle>&dependencies;</segtitle> -<sect2 role="installation"> -<title>Installation of Binutils + + Bash, Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, M4, + Make, Perl, Sed, and Texinfo + + -Verify that the PTYs are working properly inside the chroot -environment. Check that everything is set up correctly by performing a -simple test: + + + + Installation of Binutils + + Verify that the PTYs are working properly inside the chroot + environment. Check that everything is set up correctly by performing a + simple test: expect -c "spawn ls" -If the following message shows up, the chroot environment is not -set up for proper PTY operation: + If the following message shows up, the chroot environment is not + set up for proper PTY operation: -The system has no more ptys. +The system has no more ptys. Ask your system administrator to create more. -This issue needs to be resolved before running the test suites -for Binutils and GCC. + This issue needs to be resolved before running the test suites + for Binutils and GCC. -The Binutils documentation recommends building Binutils outside of the -source directory in a dedicated build directory: + The Binutils documentation recommends building Binutils outside of the + source directory in a dedicated build directory: mkdir -v ../binutils-build cd ../binutils-build -Prepare Binutils for compilation: + Prepare Binutils for compilation: ../binutils-&binutils-version;/configure --prefix=/usr \ --enable-shared -Compile the package: + Compile the package: make tooldir=/usr - - The meaning of the make parameter: - - tooldir=/usr - - Normally, the tooldir (the directory where the executables will - ultimately be located) is set to $(exec_prefix)/$(target_alias). For - example, i686 machines would expand that to /usr/i686-pc-linux-gnu. Because this is - a custom system, this target-specific directory in /usr is not required. $(exec_prefix)/$(target_alias) would be - used if the system was used to cross-compile (for example, compiling a - package on an Intel machine that generates code that can be executed - on PowerPC machines). - - - - -The test suite for Binutils in this section is -considered critical. Do not skip it under any -circumstances. - -Test the results: + + The meaning of the make parameter: + + + tooldir=/usr + + Normally, the tooldir (the directory where the executables will + ultimately be located) is set to $(exec_prefix)/$(target_alias). For + example, i686 machines would expand that to /usr/i686-pc-linux-gnu. Because this is + a custom system, this target-specific directory in /usr is not required. $(exec_prefix)/$(target_alias) would be + used if the system was used to cross-compile (for example, compiling a + package on an Intel machine that generates code that can be executed + on PowerPC machines). + + + + + + + The test suite for Binutils in this section is considered critical. + Do not skip it under any circumstances. + + + Test the results: make check -Install the package: + Install the package: make tooldir=/usr install -Install the libiberty header file that is needed by -some packages: + Install the libiberty header + file that is needed by some packages: cp -v ../binutils-&binutils-version;/include/libiberty.h /usr/include - - - -Contents of Binutils - - -Installed programs -Installed libraries -addr2line, ar, as, c++filt, gprof, ld, nm, objcopy, objdump, -ranlib, readelf, size, strings, and strip -libiberty.a, libbfd.[a,so], and libopcodes.[a,so] - - -Short Descriptions - - - - -addr2line - -Translates program addresses to file names and line numbers; -given an address and the name of an executable, it uses the debugging -information in the executable to determine which source file and line -number are associated with the address -addr2line - - - - -ar - -Creates, modifies, and extracts from archives -ar - - - - -as - -An assembler that assembles the output of gcc -into object files -as - - - - -c++filt - -Used by the linker to de-mangle C++ and Java symbols and to keep -overloaded functions from clashing -c++filt - - - - -gprof - -Displays call graph profile data -gprof - - - - -ld - -A linker that combines a number of object and archive files into a single file, -relocating their data and tying up symbol references -ld - - - - -nm - -Lists the symbols occurring in a given object file -nm - - - - -objcopy - -Translates one type of object file into another -objcopy - - - - -objdump - -Displays information about the given object file, with options -controlling the particular information to display; the information -shown is useful to programmers who are working on the compilation -tools -objdump - - - - -ranlib - -Generates an index of the contents of an archive and stores it -in the archive; the index lists all of the symbols defined by archive -members that are relocatable object files -ranlib - - - - -readelf - -Displays information about ELF type binaries -readelf - - - - -size - -Lists the section sizes and the total size for the given object files -size - - - - -strings - -Outputs, for each given file, the sequences of printable -characters that are of at least the specified length (defaulting to -four); for object files, it prints, by default, only the strings from -the initializing and loading sections while for other types of files, it -scans the entire file -strings - - - - -strip - -Discards symbols from object files -strip - - - - -libiberty - -Contains routines used by various GNU programs, including -getopt, obstack, -strerror, strtol, and -strtoul -libiberty - - - - -libbfd - -The Binary File Descriptor library -libbfd - - - - -libopcodes - -A library for dealing with opcodes—the readable -text versions of instructions for the processor; -it is used for building utilities like -objdump. -libopcodes - - - - - + + + + + Contents of Binutils + + + Installed programs + Installed libraries + + + addr2line, ar, as, c++filt, gprof, ld, nm, objcopy, objdump, + ranlib, readelf, size, strings, and strip + libiberty.a, libbfd.[a,so], and libopcodes.[a,so] + + + + + Short Descriptions + + + + + addr2line + + Translates program addresses to file names and line numbers; + given an address and the name of an executable, it uses the debugging + information in the executable to determine which source file and line + number are associated with the address + + addr2line + + + + + + ar + + Creates, modifies, and extracts from archives + + ar + + + + + + as + + An assembler that assembles the output of gcc + into object files + + as + + + + + + c++filt + + Used by the linker to de-mangle C++ and Java symbols and to keep + overloaded functions from clashing + + c++filt + + + + + + gprof + + Displays call graph profile data + + gprof + + + + + + ld + + A linker that combines a number of object and archive files + into a single file, relocating their data and tying up symbol + references + + ld + + + + + + nm + + Lists the symbols occurring in a given object file + + nm + + + + + + objcopy + + Translates one type of object file into another + + objcopy + + + + + + objdump + + Displays information about the given object file, with options + controlling the particular information to display; the information + shown is useful to programmers who are working on the compilation + tools + + objdump + + + + + + ranlib + + Generates an index of the contents of an archive and stores it + in the archive; the index lists all of the symbols defined by archive + members that are relocatable object files + + ranlib + + + + + + readelf + + Displays information about ELF type binaries + + readelf + + + + + + size + + Lists the section sizes and the total size for the given + object files + + size + + + + + + strings + + Outputs, for each given file, the sequences of printable + characters that are of at least the specified length (defaulting to + four); for object files, it prints, by default, only the strings from + the initializing and loading sections while for other types of files, it + scans the entire file + + strings + + + + + + strip + + Discards symbols from object files + + strip + + + + + + libiberty + + Contains routines used by various GNU programs, including + getopt, obstack, + strerror, strtol, and + strtoul + + libiberty + + + + + + libbfd + + The Binary File Descriptor library + + libbfd + + + + + + libopcodes + + A library for dealing with opcodes—the readable + text versions of instructions for the processor; + it is used for building utilities like + objdump. + + libopcodes + + + + + + + - -- cgit v1.2.3-54-g00ecf