Changeset 3f0c882 for chapter06/binutils.xml
- Timestamp:
- 12/21/2004 07:38:32 PM (19 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 3d36131c
- Parents:
- aaa3260
- File:
-
- 1 edited
-
chapter06/binutils.xml (modified) (8 diffs)
Legend:
- Unmodified
- Added
- Removed
-
chapter06/binutils.xml
raaa3260 r3f0c882 11 11 12 12 <sect2 role="package"><title/> 13 <para>The Binutils package contains a linker, an assembler, and other tools for14 handling object files.</para>15 13 16 14 <segmentedlist> … … 20 18 </segmentedlist> 21 19 22 <segmentedlist>23 <segtitle>Binutils installation depends on</segtitle>24 <seglistitem><seg>Bash, Coreutils, Diffutils, GCC, Gettext,25 Glibc, Grep, Make, Perl, Sed, Texinfo</seg></seglistitem>26 </segmentedlist>27 20 </sect2> 28 21 … … 30 23 <title>Installation of Binutils</title> 31 24 32 <para>Now is an appropriate time to verify that your pseudo terminals (PTYs) are 33 working properly inside the chroot environment. We will again quickly check that 34 everything is set up correctly by performing a simple test:</para> 25 <para>Check if there is PTYs for the test suites:</para> 35 26 36 27 <screen><userinput>expect -c "spawn ls"</userinput></screen> 37 38 <para>If you receive the message:</para>39 40 <screen><computeroutput>The system has no more ptys. Ask your system administrator to create more.</computeroutput></screen>41 42 <para>Your chroot environment is not set up for proper PTY operation. In this43 case there is no point in running the test suites for Binutils and GCC until you44 are able to resolve the issue.</para>45 46 <para>This package is known to behave badly when you have changed its47 default optimization flags (including the <parameter>-march</parameter> and <parameter>-mcpu</parameter> options).48 Therefore, if you have defined any environment variables that override49 default optimizations, such as CFLAGS and CXXFLAGS, we recommend un-setting50 or modifying them when building Binutils.</para>51 28 52 29 <para>The current version of Binutils in use has a bug that causes strip to … … 56 33 <screen><userinput>patch -Np1 -i ../binutils-&binutils-version;-fix_strip-1.patch</userinput></screen> 57 34 58 <para>The Binutils documentation recommends building Binutils outside of the 59 source directory in a dedicated build directory:</para> 35 <para>Create the build directory:</para> 60 36 61 37 <screen><userinput>mkdir ../binutils-build … … 70 46 <screen><userinput>make tooldir=/usr</userinput></screen> 71 47 72 <para>Normally, the <emphasis>tooldir</emphasis> (the directory where the73 executables end up) is set to $(exec_prefix)/$(target_alias), which expands74 into, for example, <filename class="directory">/usr/i686-pc-linux-gnu</filename>. Since we only75 build for our own system, we don't need this target specific directory in76 <filename class="directory">/usr</filename>. That setup would be used if the system was used to77 cross-compile (for example compiling a package on an Intel machine that78 generates code that can be executed on PowerPC machines).</para>79 80 <important><para>The test suite for Binutils in this section is considered81 <emphasis>critical</emphasis>. Our advice is to not skip it under any82 circumstances.</para></important>83 84 48 <para>Test the results:</para> 85 49 … … 87 51 88 52 <para>The test suite notes from <xref linkend="ch-tools-binutils-pass2"/> are still 89 very much appropriate here. Be sure to refer back there should you have any 90 doubts.</para> 53 very much appropriate here..</para> 91 54 92 55 <para>Install the package:</para> … … 94 57 <screen><userinput>make tooldir=/usr install</userinput></screen> 95 58 96 <para>Install the <filename class="headerfile">libiberty</filename> header file that is needed by 97 some packages:</para> 59 <para>Install the <filename class="headerfile">libiberty</filename> header file:</para> 98 60 99 61 <screen><userinput>cp ../binutils-&binutils-version;/include/libiberty.h /usr/include</userinput></screen> … … 104 66 <sect2 id="contents-binutils" role="content"><title>Contents of Binutils</title> 105 67 106 <segmentedlist> 107 <segtitle>Installed programs</segtitle> 108 <segtitle>Installed libraries</segtitle> 109 <seglistitem><seg>addr2line, ar, as, c++filt, gprof, ld, nm, objcopy, objdump, 110 ranlib, readelf, size, strings and strip</seg> 111 <seg>libiberty.a, libbfd.[a,so] and libopcodes.[a,so]</seg></seglistitem> 112 </segmentedlist> 113 114 <variablelist><title>Short descriptions</title> 115 116 <varlistentry id="addr2line"> 117 <term><command>addr2line</command></term> 118 <listitem> 119 <indexterm zone="ch-system-binutils addr2line"><primary sortas="b-addr2line">addr2line</primary></indexterm> 120 <para>translates program addresses to file 121 names and line numbers. Given an address and the name of an executable, it 122 uses the debugging information in the executable to figure out which source 123 file and line number are associated with the address.</para> 124 </listitem> 125 </varlistentry> 126 127 <varlistentry id="ar"> 128 <term><command>ar</command></term> 129 <listitem> 130 <indexterm zone="ch-system-binutils ar"><primary sortas="b-ar">ar</primary></indexterm> 131 <para>creates, modifies, and extracts from archives. An archive 132 is a single file holding a collection of other files in a structure that makes 133 it possible to retrieve the original individual files (called members of 134 the archive).</para> 135 </listitem> 136 </varlistentry> 137 138 <varlistentry id="as"> 139 <term><command>as</command></term> 140 <listitem> 141 <indexterm zone="ch-system-binutils as"><primary sortas="b-as">as</primary></indexterm> 142 <para>is an assembler. It assembles the output of <command>gcc</command> into object files.</para> 143 </listitem> 144 </varlistentry> 145 146 <varlistentry id="c-filt"> 147 <term><command>c++filt</command></term> 148 <listitem> 149 <indexterm zone="ch-system-binutils c-filt"><primary sortas="b-c++filt">c++filt</primary></indexterm> 150 <para>is used by the linker to de-mangle C++ and 151 Java symbols, to keep overloaded functions from clashing.</para> 152 </listitem> 153 </varlistentry> 154 155 <varlistentry id="gprof"> 156 <term><command>gprof</command></term> 157 <listitem> 158 <indexterm zone="ch-system-binutils gprof"><primary sortas="b-gprof">gprof</primary></indexterm> 159 <para>displays call graph profile data.</para> 160 </listitem> 161 </varlistentry> 162 163 <varlistentry id="ld"> 164 <term><command>ld</command></term> 165 <listitem> 166 <indexterm zone="ch-system-binutils ld"><primary sortas="b-ld">ld</primary></indexterm> 167 <para>is a linker. It combines a number of object and archive files into a single file, 168 relocating their data and tying up symbol references.</para> 169 </listitem> 170 </varlistentry> 171 172 <varlistentry id="nm"> 173 <term><command>nm</command></term> 174 <listitem> 175 <indexterm zone="ch-system-binutils nm"><primary sortas="b-nm">nm</primary></indexterm> 176 <para>lists the symbols occurring in a given object file.</para> 177 </listitem> 178 </varlistentry> 179 180 <varlistentry id="objcopy"> 181 <term><command>objcopy</command></term> 182 <listitem> 183 <indexterm zone="ch-system-binutils objcopy"><primary sortas="b-objcopy">objcopy</primary></indexterm> 184 <para>is used to translate one type of object file into another.</para> 185 </listitem> 186 </varlistentry> 187 188 <varlistentry id="objdump"> 189 <term><command>objdump</command></term> 190 <listitem> 191 <indexterm zone="ch-system-binutils objdump"><primary sortas="b-objdump">objdump</primary></indexterm> 192 <para>displays information about the given object file, with options controlling what 193 particular information to display. The information shown is mostly only useful to 194 programmers who are working on the compilation tools.</para> 195 </listitem> 196 </varlistentry> 197 198 <varlistentry id="ranlib"> 199 <term><command>ranlib</command></term> 200 <listitem> 201 <indexterm zone="ch-system-binutils ranlib"><primary sortas="b-ranlib">ranlib</primary></indexterm> 202 <para>generates an index of the contents of an 203 archive, and stores it in the archive. The index lists all the symbols defined 204 by archive members that are relocatable object files.</para> 205 </listitem> 206 </varlistentry> 207 208 <varlistentry id="readelf"> 209 <term><command>readelf</command></term> 210 <listitem> 211 <indexterm zone="ch-system-binutils readelf"><primary sortas="b-readelf">readelf</primary></indexterm> 212 <para>displays information about elf type binaries.</para> 213 </listitem> 214 </varlistentry> 215 216 <varlistentry id="size"> 217 <term><command>size</command></term> 218 <listitem> 219 <indexterm zone="ch-system-binutils size"><primary sortas="b-size">size</primary></indexterm> 220 <para>lists the section sizes -- and the grand total -- for the given object files.</para> 221 </listitem> 222 </varlistentry> 223 224 <varlistentry id="strings"> 225 <term><command>strings</command></term> 226 <listitem> 227 <indexterm zone="ch-system-binutils strings"><primary sortas="b-strings">strings</primary></indexterm> 228 <para>outputs, for each given file, the sequences 229 of printable characters that are of at least the specified length (defaulting to 4). 230 For object files it prints, by default, only the strings from the initializing 231 and loading sections. For other types of files it scans the whole file.</para> 232 </listitem> 233 </varlistentry> 234 235 <varlistentry id="strip"> 236 <term><command>strip</command></term> 237 <listitem> 238 <indexterm zone="ch-system-binutils strip"><primary sortas="b-strip">strip</primary></indexterm> 239 <para>discards symbols from object files.</para> 240 </listitem> 241 </varlistentry> 242 243 <varlistentry id="libiberty"> 244 <term><filename class="libraryfile">libiberty</filename></term> 245 <listitem> 246 <indexterm zone="ch-system-binutils libiberty"><primary sortas="c-libiberty">libiberty</primary></indexterm> 247 <para>contains routines used by various GNU 248 programs, including getopt, obstack, strerror, strtol and strtoul.</para> 249 </listitem> 250 </varlistentry> 251 252 <varlistentry id="libbfd"> 253 <term><filename class="libraryfile">libbfd</filename></term> 254 <listitem> 255 <indexterm zone="ch-system-binutils libbfd"><primary sortas="c-libbfd">libbfd</primary></indexterm> 256 <para>is the Binary File Descriptor library.</para> 257 </listitem> 258 </varlistentry> 259 260 <varlistentry id="libopcodes"> 261 <term><filename class="libraryfile">libopcodes</filename></term> 262 <listitem> 263 <indexterm zone="ch-system-binutils libopcodes"><primary sortas="c-libopcodes">libopcodes</primary></indexterm> 264 <para>is a library for dealing with opcodes. 265 It is used for building utilities like objdump. Opcodes are the <quote>readable 266 text</quote> versions of instructions for the processor.</para> 267 </listitem> 268 </varlistentry> 269 </variablelist> 68 <para>See testing</para> 270 69 271 70 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.
