Changeset 3c928f1 for chapter06/binutils.xml
- Timestamp:
- 06/13/2004 12:58:23 PM (20 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.0, 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:
- e63529b
- Parents:
- 7db6ac5
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/binutils.xml
r7db6ac5 r3c928f1 38 38 <para>If you receive the message:</para> 39 39 40 < blockquote><screen>The system has no more ptys. Ask your system administrator to create more.</screen></blockquote>40 <screen><computeroutput>The system has no more ptys. Ask your system administrator to create more.</computeroutput></screen> 41 41 42 42 <para>Your chroot environment is not set up for proper PTY operation. In this … … 45 45 46 46 <para>This package is known to behave badly when you have changed its 47 default optimization flags (including the -march and -mcpuoptions).47 default optimization flags (including the <parameter>-march</parameter> and <parameter>-mcpu</parameter> options). 48 48 Therefore, if you have defined any environment variables that override 49 49 default optimizations, such as CFLAGS and CXXFLAGS, we recommend un-setting … … 66 66 <para>Normally, the <emphasis>tooldir</emphasis> (the directory where the 67 67 executables end up) is set to $(exec_prefix)/$(target_alias), which expands 68 into, for example, <filename >/usr/i686-pc-linux-gnu</filename>. Since we only68 into, for example, <filename class="directory">/usr/i686-pc-linux-gnu</filename>. Since we only 69 69 build for our own system, we don't need this target specific directory in 70 <filename >/usr</filename>. That setup would be used if the system was used to70 <filename class="directory">/usr</filename>. That setup would be used if the system was used to 71 71 cross-compile (for example compiling a package on an Intel machine that 72 72 generates code that can be executed on PowerPC machines).</para> … … 88 88 <screen><userinput>make tooldir=/usr install</userinput></screen> 89 89 90 <para>Install the < emphasis>libiberty</emphasis> header file that is needed by90 <para>Install the <filename class="headerfile">libiberty</filename> header file that is needed by 91 91 some packages:</para> 92 92 … … 134 134 <listitem> 135 135 <indexterm zone="ch-system-binutils as"><primary sortas="b-as">as</primary></indexterm> 136 <para>is an assembler. It assembles the output of gccinto object files.</para>136 <para>is an assembler. It assembles the output of <command>gcc</command> into object files.</para> 137 137 </listitem> 138 138 </varlistentry>
Note:
See TracChangeset
for help on using the changeset viewer.