chapter05/grep.xml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

<sect1 id="ch05-grep">
<title>Installing Grep-&grep-version;</title>
<?dbhtml filename="grep.html" dir="chapter05"?>

<screen>Estimated build time:           &grep-time-tools;
Estimated required disk space:  &grep-compsize-tools;</screen>

&aa-grep-shortdesc;
&aa-grep-dep;

<sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>

<sect2>
<title>Installation of Grep</title>

<para>Prepare Grep for compilation:</para>

<screen><userinput>./configure --prefix=/tools \
&nbsp;&nbsp;&nbsp;&nbsp;--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, but 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 it, it 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>This package has a test suite available which can perform a number of
checks to ensure it built correctly.  Should you choose to run it, 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>

</sect1>