Ignore:
Timestamp:
08/29/2004 06:36:34 PM (20 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
6.0
Children:
8b320e7
Parents:
ec0a37e6
Message:

Second round of edits for final release

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter05/gcc-pass2.xml

    rec0a37e6 r69993f4  
    3434unset them when building GCC.</para>
    3535
    36 <para>The tools required to test GCC and Binutils -- Tcl, Expect and
    37 DejaGNU -- are installed now. GCC and Binutils can now be rebuilt,
    38 linking them against the new Glibc and testing them properly (if
    39 running the test suites in this chapter). Please note that these test
    40 suites are highly dependent on properly functioning pseudo terminals
    41 (PTYs) which are provided by the host. PTYs are most commonly
    42 implemented via the <systemitem class="filesystem">devpts</systemitem>
    43 file system. Check to see if the host system is set up correctly in
    44 this regard by performing a quick test:</para>
     36<para>The tools required to test GCC and Binutils&mdash;Tcl, Expect
     37and DejaGNU&mdash;are installed now. GCC and Binutils can now be
     38rebuilt, linking them against the new Glibc and testing them properly
     39(if running the test suites in this chapter). Please note that these
     40test suites are highly dependent on properly functioning PTYs which
     41are provided by the host. PTYs are most commonly implemented via the
     42<systemitem class="filesystem">devpts</systemitem> file system. Check
     43to see if the host system is set up correctly in this regard by
     44performing a quick test:</para>
    4545
    4646<screen><userinput>expect -c "spawn ls"</userinput></screen>
    … …  
    5757
    5858<para>Because the C and the C++ compilers will be built, unpack both
    59 the core and the g++ tarballs (as well as testsuite, if you want to
     59the core and the g++ tarballs (as well as test suite, if you want to
    6060run the tests). By unpacking them in the working directory, they will
    6161all unfold into a single <filename
    … …  
    7474Glibc header files on the host system need to be fixed, and will fix
    7575them and put them in the GCC private include directory. In <xref
    76 linkend="chapter-building-system"/>, after the newer Glibc had been
     76linkend="chapter-building-system"/>, after the newer Glibc has been
    7777installed, this private include directory will be searched before the
    7878system include directory.  This may result in GCC finding the fixed
    … …  
    136136statics and global objects.  This option is essential for fully
    137137standards-compliant handling of destructors. It also affects the C++
    138 ABI and therefore results in C++ shared libraries and C++ programs
     138ABI, and therefore results in C++ shared libraries and C++ programs
    139139that are interoperable with other Linux
    140140distributions.</para></listitem>
    … …  
    187187url="http://gcc.gnu.org/ml/gcc-testresults/2004-07/msg00179.html"/>.</para>
    188188
    189 <para>Having a few unexpected failures often cannot be avoided. The
     189<para>A few unexpected failures cannot always be avoided. The
    190190GCC developers are usually aware of these issues, but have not
    191191resolved them yet. Unless the test results are vastly different from
    … …  
    205205
    206206<sect2 role="content"><title/>
    207 <para>The details on this package are found in <xref linkend="contents-gcc"/>.</para>
     207<para>Details on this package are located in <xref linkend="contents-gcc"/>.</para>
    208208</sect2>
    209209
Note: See TracChangeset for help on using the changeset viewer.