Ignore:
Timestamp:
07/27/2005 08:12:03 PM (19 years ago)
Author:
Randy McMurchy <randy@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
40d6bab
Parents:
a2de57a7
Message:

Removed the mention of the GCC testsuite tarball from the GCC instructions as the testsuite is already included in the GCC release tarball

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@4805 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • general/prog/gcc.xml

    ra2de57a7 r4ea5113  
    1616  <!ENTITY gnat-md5sum        "57c060cd1ccef8b1ae9165b11d98780a">
    1717  <!ENTITY gnat-size          "13.4 MB">
    18   <!ENTITY gnat-time          "0.01 SBU">
    19 
    20   <!ENTITY gcc-testsuite-url    "http://mirrors.rcn.net/pub/sourceware/gcc/releases/gcc-&gcc-version;/gcc-testsuite-&gcc-version;.tar.bz2">
    21   <!ENTITY gcc-testsuite-md5sum "b4fff6ce0a038021b9e507917abb9a07">
     18  <!ENTITY gnat-time          "less than 0.1 SBU">
    2219]>
    2320
     
    7673        <para>Required patch: <ulink
    7774        url="&patch-root;/gcc-&gcc-version;-linkonce-1.patch"/></para>
    78       </listitem>
    79       <listitem>
    80         <para>Test suite: <ulink url="&gcc-testsuite-url;"/></para>
    81       </listitem>
    82       <listitem>
    83         <para>Test suite MD5 sum: &gcc-testsuite-md5sum;</para>
    8475      </listitem>
    8576    </itemizedlist>
     
    175166      is highly recommended that you have the <application>Tcl</application>,
    176167      <application>Expect</application> and <application>DejaGnu</application>
    177       packages installed, as well as unpacking the <application>GCC</application>
    178       testsuite tarball before beginning the build.</para>
     168      packages installed before beginning the build so you can run the full
     169      suite of tests.</para>
    179170
    180171      <para>Do not continue with the <command>make install</command> command
    181       until you're confident the build was successful. You can compare your test results
    182       with those found at <ulink url="http://gcc.gnu.org/ml/gcc-testresults/"/>. There's
    183       also an i686 platform test result produced by an LFS-SVN-20050316 system at
    184       <ulink url="http://linuxfromscratch.org/~randy/gcc343_test.txt"/>. You may also
    185       want to refer to the information found in the
     172      until you're confident the build was successful. You can compare your
     173      test results with those found at
     174      <ulink url="http://gcc.gnu.org/ml/gcc-testresults/"/>. There's also an
     175      i686 platform test result produced by an LFS-6.1 system at
     176      <ulink url="http://linuxfromscratch.org/~randy/gcc343_test.txt"/>. You
     177      may also want to refer to the information found in the
    186178      <application>GCC</application>-Pass 2 section of Chapter 5 in the LFS book
    187179      (<ulink url="&lfs-root;/chapter05/gcc-pass2.html"/>).</para>
    188180    </important>
    189 
    190     <note>
    191       <para>Some of the <application>Java</application> programs installed by
    192       the <application>GCC</application> package conflict (have the same names)
    193       with programs from the <xref linkend="jdk"/> package. If you're installing the
    194       <application>Java</application> language from the
    195       <application>GCC</application> package but you wish to use the programs
    196       from the <application>JDK</application> as the defaults, ensure
    197       <filename class='directory'>$JAVA_HOME/bin</filename> is listed before
    198       <filename class='directory'>/usr/bin</filename> in your <envar>PATH</envar>
    199       variable after the <application>GCC</application> installation is complete.</para>
    200     </note>
    201181
    202182<screen><userinput>patch -Np1 -i ../gcc-&gcc-version;-no_fixincludes-1.patch &amp;&amp;
     
    246226<screen><userinput>export PATH=$PATH_HOLD &amp;&amp;
    247227unset PATH_HOLD</userinput></screen>
     228
     229    <note>
     230      <para>Some of the <application>Java</application> programs installed by
     231      the <application>GCC</application> package conflict (have the same names)
     232      with programs from the <xref linkend="jdk"/> package. If you installed
     233      the <application>Java</application> language from the
     234      <application>GCC</application> package but you wish to use the programs
     235      from the <application>JDK</application> as the defaults, ensure
     236      <filename class='directory'>$JAVA_HOME/bin</filename> is listed before
     237      <filename class='directory'>/usr/bin</filename> in your
     238      <envar>PATH</envar> variable.</para>
     239    </note>
    248240
    249241  </sect2>
     
    640632
    641633</sect1>
    642 
Note: See TracChangeset for help on using the changeset viewer.