source: BOOK/cross-tools/x86/gcc-static.xml @ cf66ceae

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
  <!ENTITY % general-entities SYSTEM "../../general.ent">
  <!ENTITY % patches-entities SYSTEM "../../patches.ent">
  %general-entities;
  %patches-entities;
]>

<sect1 id="ch-cross-tools-gcc-static" role="wrap">
  <?dbhtml filename="gcc-static.html"?>

  <title>Cross GCC-&gcc-version; - Static</title>

  <indexterm zone="ch-cross-tools-gcc-static">
    <primary sortas="a-GCC">GCC</primary>
    <secondary>cross tools, static</secondary>
  </indexterm>

  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
  href="../../final-system/common/gcc.xml"
  xpointer="xpointer(//*[@role='package'])"/>

  <sect2 role="installation">
    <title>Installation of Cross GCC Compiler with Static libgcc
    and no Threads</title>

    <para os="aa">We will make a couple of essential adjustments to the specs file
    to point to use our build environment:</para>

<screen os="ab"><userinput>patch -Np1 -i ../&gcc-specs-patch;</userinput></screen>

    <para os="ac">To make sure that we use the proper syntax for a couple of tools,
    we apply the following patch:</para>

<screen os="ad"><userinput>patch -Np1 -i ../&gcc-posix-patch;</userinput></screen>

    <para os="ae">The following patch ensures that <command>gcc</command> does not
    search the <filename class="directory">/usr</filename> directory for
    <filename class="libraryfile">libgcc_s.so</filename> when
    cross-compling:</para>

<screen os="af"><userinput>patch -Np1 -i ../&gcc-cross_search-patch;</userinput></screen>

    <para os="ag">Now we will need to setup our StartFile Spec to the correct library
    location:</para>

<screen os="ah"><userinput>echo "
#undef STARTFILE_PREFIX_SPEC
#define STARTFILE_PREFIX_SPEC \"/tools/lib/\"" &gt;&gt; gcc/config/linux.h</userinput></screen>

    <para os="ai">Now we will change <command>gcc</command>'s search path to look
    into <filename class="directory">/tools</filename> only:</para>

<screen os="aj"><userinput>cp gcc/Makefile.in{,.orig}
sed -e "s@\(^CROSS_SYSTEM_HEADER_DIR =\).*@\1 /tools/include@g" \
 gcc/Makefile.in.orig > gcc/Makefile.in</userinput></screen>

    <important os="ak">
      <para>The above patches and sed's are critical in ensuring a
      successful overall build. Do not forget to apply them.</para>
    </important>

    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
    href="../../final-system/common/gcc.xml"
    xpointer="xpointer(//*[@os='f'])"/>

    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
    href="../../final-system/common/gcc.xml"
    xpointer="xpointer(//*[@os='g'])"/>

    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
    href="../../final-system/common/gcc.xml"
    xpointer="xpointer(//*[@os='h'])"/>

<screen><userinput>../gcc-&gcc-version;/configure --prefix=/cross-tools \
    --host=${LFS_HOST} --target=${LFS_TARGET} \
    --with-local-prefix=/tools --disable-nls --disable-shared \
    --disable-threads --enable-languages=c</userinput></screen>

    <variablelist os="al">
      <title>The meaning of the configure options:</title>

     <varlistentry>
        <term><parameter>--with-local-prefix=/tools</parameter></term>
        <listitem>
          <para>The purpose of this switch is to remove <filename
          class="directory">/usr/local/include</filename> from
          <command>gcc</command>'s include search path. This is not
          absolutely essential, however, it helps to minimize the
          influence of the host system.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><parameter>--disable-shared</parameter></term>
        <listitem>
          <para>Disables the creation of the shared libraries.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><parameter>--disable-threads</parameter></term>
        <listitem>
          <para>This will prevent GCC from finding the multi-thread
          include files, since we haven't created them for this architecture
          yet. We will be able to find the multi-thread information after
          we create the Glibc headers.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><parameter>--enable-languages=c</parameter></term>
        <listitem>
          <para>This option ensures that only the C compiler is built.</para>
        </listitem>
      </varlistentry>

    </variablelist>

    <para>Continue with compiling the package:</para>

<screen><userinput>make all-gcc</userinput></screen>

    <para>Install the package:</para>

<screen><userinput>make install-gcc</userinput></screen>

  </sect2>

  <sect2 role="content">
    <title/>

    <para>Details on this package are located in <xref
    linkend="contents-gcc" role="."/></para>

  </sect2>

</sect1>