|
@@ -36,7 +36,7 @@ afterwards.</para></note>
|
|
|
|
|
|
<para>Prepare Zlib for compilation:</para>
|
|
|
|
|
|
-<screen><userinput>./configure --prefix=/usr --shared</userinput></screen>
|
|
|
+<screen><userinput>./configure --prefix=/usr --shared --libdir=/lib</userinput></screen>
|
|
|
|
|
|
<para>Compile the package:</para>
|
|
|
|
|
@@ -66,26 +66,6 @@ make</userinput></screen>
|
|
|
|
|
|
<screen><userinput>chmod 644 /usr/lib/libz.a</userinput></screen>
|
|
|
|
|
|
-<para>It is good policy and common practice to place important libraries into
|
|
|
-the <filename class="directory">/lib</filename> directory. This matters most
|
|
|
-in scenarios where <filename class="directory">/usr</filename> is on a
|
|
|
-separate partition. Essentially, the run-time components of any libraries that
|
|
|
-are used by programs in <filename class="directory">/bin</filename> or
|
|
|
-<filename class="directory">/sbin</filename> should reside in
|
|
|
-<filename class="directory">/lib</filename> so that they are on the root
|
|
|
-partition and available in the event of
|
|
|
-<filename class="directory">/usr</filename> being inaccessible.</para>
|
|
|
-
|
|
|
-<para>For the above reason we move the run-time components of the shared Zlib
|
|
|
-into <filename class="directory">/lib</filename>:</para>
|
|
|
-
|
|
|
-<screen><userinput>mv /usr/lib/libz.so.* /lib</userinput></screen>
|
|
|
-
|
|
|
-<para>Now we need to fix the <filename class="symlink">/usr/lib/libz.so</filename> symlink
|
|
|
-because we just moved the file it points to:</para>
|
|
|
-
|
|
|
-<screen><userinput>ln -sf ../../lib/libz.so.1 /usr/lib/libz.so</userinput></screen>
|
|
|
-
|
|
|
</sect2>
|
|
|
|
|
|
|