glfs/general/prog/gcc2.xml
Bruce Dubbs 52d29f7a42 XML Updates to Part III from DJ
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@2304 af4574ff-66df-0310-9fd7-8a98e5e911e0
2004-06-12 22:56:28 +00:00

89 lines
4.3 KiB
XML

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
<!ENTITY % general-entities SYSTEM "../../general.ent">
%general-entities;
<!ENTITY gcc2-download-http "http://ftp.gnu.org/gnu/gcc/gcc-&gcc2-version;.tar.gz">
<!ENTITY gcc2-download-ftp "ftp://ftp.gnu.org/gnu/gcc/gcc-&gcc2-version;.tar.gz">
<!ENTITY gcc2-size "9.4 MB">
<!ENTITY gcc2-buildsize "150 MB">
<!ENTITY gcc2-time "2.60 SBU">
]>
<sect1 id="gcc2" xreflabel="GCC-&gcc2-version;">
<?dbhtml filename="gcc2.html" ?>
<title>GCC-&gcc2-version;</title>
<sect2>
<title>Introduction to <application><acronym>GCC</acronym></application>-&gcc2-version;</title>
<para>There are two reasons for installing
<acronym>GCC</acronym>-&gcc2-version;. The first is that the kernel
developers have certified <acronym>GCC</acronym>-&gcc2-version; as the
preferred compiler for compiling the kernel. The other (and more compelling
reason) is that some commercial closed-source packages (such as Netscape
Navigator, Yahoo Pager) and precompiled packages (such as Mozilla)
are linked against <acronym>GCC</acronym>-&gcc2-version; libs.</para>
<sect3><title>Package information</title>
<itemizedlist spacing='compact'>
<listitem><para>Download (HTTP): <ulink
url="&gcc2-download-http;"/></para></listitem>
<listitem><para>Download (FTP): <ulink
url="&gcc2-download-ftp;"/></para></listitem>
<listitem><para>Download size: &gcc2-size;</para></listitem>
<listitem><para>Estimated Disk space required:
&gcc2-buildsize;</para></listitem>
<listitem><para>Estimated build time:
&gcc2-time;</para></listitem></itemizedlist>
</sect3>
<sect3><title>Additional downloads</title>
<itemizedlist spacing='compact'>
<listitem><para><ulink url="&patch-root;/gcc-2.95.3-2.patch"/></para></listitem>
<listitem><para><ulink url="&patch-root;/gcc-2.95.3-no-fixinc.patch"/></para></listitem>
<listitem><para><ulink url="&patch-root;/gcc-2.95.3-returntype-fix.patch"/></para></listitem>
</itemizedlist>
</sect3>
</sect2>
<sect2>
<title>Configuring <application><acronym>GCC</acronym></application></title>
<sect3><title>Configuration Information</title>
<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../../lib-config.xml"/>
<para>The instructions given above make compatibility symlinks that pre-compiled
packages in <acronym>BLFS</acronym> require. You may create additional
compatibility links based on your requirements.</para>
<para>If you only need the GCC-&gcc2-version; libraries, you may delete
<filename>/opt/gcc-&gcc2-version;</filename>.</para>
<para>Whenever you need to use GCC-&gcc2-version; instead of your system
installed compiler, add
<filename class="directory">/opt/gcc-&gcc2-version;/bin</filename> to the front of your <envar>PATH</envar> or (preferably) set the <envar>CC</envar>
environment variable before compiling the concerned package.</para>
</sect3>
</sect2>
<sect2>
<title>Contents</title>
<para>The GCC-&gcc2-version; package contains the
<command>gcc</command>-&gcc2-version; <application>C</application> and
<application>C++</application> compilers and GCC-&gcc2-version;
<filename>libstdc++.so</filename> that is required by some commercial and
pre-compiled packages.</para>
</sect2>
</sect1>