| 1 | <sect1 id="ch06-zlib">
|
|---|
| 2 | <title>Installing Zlib-&zlib-version;</title>
|
|---|
| 3 | <?dbhtml filename="zlib.html" dir="chapter06"?>
|
|---|
| 4 |
|
|---|
| 5 | <screen>Estimated build time: &zlib-time;
|
|---|
| 6 | Estimated required disk space: &zlib-compsize;</screen>
|
|---|
| 7 |
|
|---|
| 8 | &aa-zlib-shortdesc;
|
|---|
| 9 | &aa-zlib-dep;
|
|---|
| 10 |
|
|---|
| 11 | <sect2><title> </title><para> </para></sect2>
|
|---|
| 12 |
|
|---|
| 13 | <sect2>
|
|---|
| 14 | <title>Installation of Zlib</title>
|
|---|
| 15 |
|
|---|
| 16 | <para>Prepare Zlib for compilation:</para>
|
|---|
| 17 |
|
|---|
| 18 | <screen><userinput>./configure --prefix=/usr --shared</userinput></screen>
|
|---|
| 19 |
|
|---|
| 20 | <note><para>Zlib is known to build its shared library incorrectly if CFLAGS is
|
|---|
| 21 | specified in the environment. If you are using your own CFLAGS variable, be
|
|---|
| 22 | sure to add the <emphasis role="strong">-fPIC</emphasis> directive to your
|
|---|
| 23 | CFLAGS for the duration of the above command, then remove it
|
|---|
| 24 | afterwards.</para></note>
|
|---|
| 25 |
|
|---|
| 26 | <para>Compile the package:</para>
|
|---|
| 27 |
|
|---|
| 28 | <screen><userinput>make</userinput></screen>
|
|---|
| 29 |
|
|---|
| 30 | <para>This package has a test suite available which can perform a number of
|
|---|
| 31 | checks to ensure it built correctly. The test suite for Zlib is quick and
|
|---|
| 32 | painless so we recommend it be run. The following command will test the shared
|
|---|
| 33 | library:</para>
|
|---|
| 34 |
|
|---|
| 35 | <screen><userinput>make check</userinput></screen>
|
|---|
| 36 |
|
|---|
| 37 | <para>Install the shared library:</para>
|
|---|
| 38 |
|
|---|
| 39 | <screen><userinput>make install</userinput></screen>
|
|---|
| 40 |
|
|---|
| 41 | <para>Now also build the non-shared (static) library:</para>
|
|---|
| 42 | <screen><userinput>make clean
|
|---|
| 43 | ./configure --prefix=/usr
|
|---|
| 44 | make</userinput></screen>
|
|---|
| 45 |
|
|---|
| 46 | <para>The following command will test the static library:</para>
|
|---|
| 47 |
|
|---|
| 48 | <screen><userinput>make check</userinput></screen>
|
|---|
| 49 |
|
|---|
| 50 | <para>And install the package:</para>
|
|---|
| 51 |
|
|---|
| 52 | <screen><userinput>make install</userinput></screen>
|
|---|
| 53 |
|
|---|
| 54 | <para>It is good policy and common practice to place important libraries into
|
|---|
| 55 | the <filename class="directory">/lib</filename> directory. This matters most
|
|---|
| 56 | in scenarios where <filename class="directory">/usr</filename> is on a
|
|---|
| 57 | separate partition. Essentially, the run-time components of any libraries
|
|---|
| 58 | depended upon by programs in <filename class="directory">/bin</filename> or
|
|---|
| 59 | <filename class="directory">/sbin</filename> should reside in
|
|---|
| 60 | <filename class="directory">/lib</filename> so that they are on the root
|
|---|
| 61 | partition and available in the event of
|
|---|
| 62 | <filename class="directory">/usr</filename> being inaccessible.</para>
|
|---|
| 63 |
|
|---|
| 64 | <para>Therefore we move the run-time components of the shared Zlib into
|
|---|
| 65 | <filename class="directory">/lib</filename> by issuing the following
|
|---|
| 66 | command:</para>
|
|---|
| 67 |
|
|---|
| 68 | <screen><userinput>mv /usr/lib/libz.so.* /lib</userinput></screen>
|
|---|
| 69 |
|
|---|
| 70 | <para>Now we need to fix up the <filename>/usr/lib/libz.so</filename> symlink
|
|---|
| 71 | because we just moved the location of the file it points to:</para>
|
|---|
| 72 |
|
|---|
| 73 | <screen><userinput>ln -sf ../../lib/libz.so.1 /usr/lib/libz.so</userinput></screen>
|
|---|
| 74 |
|
|---|
| 75 | </sect2>
|
|---|
| 76 |
|
|---|
| 77 | </sect1>
|
|---|
| 78 |
|
|---|
