123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354 |
- <sect1 id="ch05-grep">
- <title>Installing Grep-&grep-version;</title>
- <?dbhtml filename="grep.html" dir="chapter05"?>
- <screen>&buildtime; &grep-time-tools;
- &diskspace; &grep-compsize-tools;</screen>
- &aa-grep-down;
- &aa-grep-dep;
- <sect2><title> </title><para> </para></sect2>
- <sect2>
- <title>Installation of Grep</title>
- <para>Prepare Grep for compilation:</para>
- <screen><userinput>./configure --prefix=/tools \
- --disable-perl-regexp --with-included-regex</userinput></screen>
- <para>The meaning of the configure options:</para>
- <itemizedlist>
- <listitem><para><userinput>--disable-perl-regexp</userinput>: This makes sure
- that <userinput>grep</userinput> does not get linked against a PCRE library
- that may be present on the host and would not be available once we enter the
- chroot environment.</para></listitem>
- <listitem><para><userinput>--with-included-regex</userinput>: This ensures that
- Grep uses its internal regular expression code. Without this switch, Grep will
- use the code from Glibc, which is known to be slightly buggy.</para></listitem>
- </itemizedlist>
- <para>Compile the programs:</para>
- <screen><userinput>make</userinput></screen>
- <para>As discussed earlier, we don't recommend running the test suites for the
- temporary tools here in this chapter. If you still want to run the Grep test
- suite anyway, the following command will do so:</para>
- <screen><userinput>make check</userinput></screen>
- <para>Then install them and their documentation:</para>
- <screen><userinput>make install</userinput></screen>
- </sect2>
- <sect2><title> </title><para> </para>
- <para>The details on this package are found in <xref linkend="contents-grep"/>.</para>
- <para> </para></sect2>
- </sect1>
|