Ignore:
Timestamp:
11/01/2003 10:31:50 PM (21 years ago)
Author:
Alex Gronenwoud <alex@…>
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, v5_0, v5_1, v5_1_1, 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:
49f4dd5
Parents:
0b400add
Message:

Merging caption and installation sections for all packages in chapters 5 and 6.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3052 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter06/binutils.xml

    r0b400add r73aedd1d  
    88&aa-binutils-shortdesc;
    99&aa-binutils-dep;
    10 &c6-binutils-inst;
     10
     11<sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>
     12
     13<sect2><title>Installation of Binutils</title>
     14
     15<para>Now is an appropriate time to verify that your pseudo terminals (PTYs) are
     16working properly inside the chroot environment. We will again quickly check that
     17everything is set up correctly by performing a simple test:</para>
     18
     19<screen><userinput>expect -c "spawn ls"</userinput></screen>
     20
     21<para>If you receive the message:</para>
     22
     23<blockquote><screen>The system has no more ptys.  Ask your system administrator to create more.</screen></blockquote>
     24
     25<para>Your chroot environment is not set up for proper PTY operation. In this
     26case there is no point in running the test suites for Binutils and GCC until you
     27are able to resolve the issue. Please refer back to <xref linkend="ch06-proc"/>
     28and <xref linkend="ch06-makedev"/> and perform the recommended steps to fix the
     29problem.</para>
     30
     31<note><para>The test suite for Binutils in this section is considered
     32<emphasis>critical</emphasis>. Our advice is to not skip it under any
     33circumstances.</para> </note>
     34
     35<para>This package is known to behave badly when you have changed its
     36default optimization flags (including the -march and -mcpu options).
     37Therefore, if you have defined any environment variables that override
     38default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
     39or modifying them when building Binutils.</para>
     40
     41<para>The Binutils documentation recommends building Binutils outside of the
     42source directory in a dedicated build directory:</para>
     43
     44<screen><userinput>mkdir ../binutils-build
     45cd ../binutils-build</userinput></screen>
     46
     47<para>Now prepare Binutils for compilation:</para>
     48
     49<screen><userinput>../binutils-&binutils-version;/configure \
     50&nbsp;&nbsp;&nbsp;&nbsp;--prefix=/usr --enable-shared</userinput></screen>
     51
     52<para>Compile the package:</para>
     53
     54<screen><userinput>make tooldir=/usr</userinput></screen>
     55
     56<para>Normally, the <emphasis>tooldir</emphasis> (the directory where the
     57executables end up) is set to $(exec_prefix)/$(target_alias), which expands
     58into, for example, <filename>/usr/i686-pc-linux-gnu</filename>. Since we only
     59build for our own system, we don't need this target specific directory in
     60<filename>/usr</filename>. That setup would be used if the system was used to
     61cross-compile (for example compiling a package on an Intel machine that
     62generates code that can be executed on PowerPC machines).</para>
     63
     64<para>Test the results:</para>
     65
     66<screen><userinput>make check</userinput></screen>
     67
     68<para>The test suite notes from <xref linkend="ch05-binutils-pass2"/> are still
     69very much appropriate here. Be sure to refer back there should you have any
     70doubts.</para>
     71
     72<para>Install the package:</para>
     73
     74<screen><userinput>make tooldir=/usr install</userinput></screen>
     75
     76<para>Install the <emphasis>libiberty</emphasis> header file that is needed by
     77some packages:</para>
     78
     79<screen><userinput>cp ../binutils-&binutils-version;/include/libiberty.h /usr/include</userinput></screen>
     80
     81</sect2>
    1182
    1283</sect1>
     84
Note: See TracChangeset for help on using the changeset viewer.