Changeset ef13657 for chapter06/zlib.xml
- Timestamp:
- 08/08/2004 02:11:09 AM (20 years ago)
- Branches:
- 6.0
- Children:
- 5ba3d1d
- Parents:
- 6e41459
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/zlib.xml
r6e41459 ref13657 29 29 <title>Installation of Zlib</title> 30 30 31 <note><para>Zlib is known to build its shared library incorrectly if CFLAGS is32 specified in the environment. If you are using your own CFLAGS variable, be 33 sure to add the <parameter>-fPIC</parameter> directive to your CFLAGS for the 34 duration of the below <command>configure</command> command, then remove it 35 afterwards.</para></note>31 <note><para>Zlib is known to build its shared library incorrectly if 32 CFLAGS is specified in the environment. If using a specified CFLAGS 33 variable, be sure to add the <parameter>-fPIC</parameter> directive to 34 the <emphasis>CFLAGS</emphasis> variable for the duration of the 35 configure command below, then remove it afterwards.</para></note> 36 36 37 37 <para>Prepare Zlib for compilation:</para> … … 50 50 <screen><userinput>make install</userinput></screen> 51 51 52 <para> Now also build the non-shared (static)library:</para>52 <para>Build the static library:</para> 53 53 54 54 <screen><userinput>make clean … … 56 56 make</userinput></screen> 57 57 58 <para>To again test the results, issue:58 <para>To test the results again, issue: 59 59 <userinput>make check</userinput>.</para> 60 60 … … 63 63 <screen><userinput>make install</userinput></screen> 64 64 65 <para> And fix the permissions on the static library:</para>65 <para>Fix the permissions on the static library:</para> 66 66 67 67 <screen><userinput>chmod 644 /usr/lib/libz.a</userinput></screen> 68 68 69 <para>It is good policy and common practice to place important libraries into 70 the <filename class="directory">/lib</filename> directory. This matters most 71 in scenarios where <filename class="directory">/usr</filename> is on a 72 separate partition. Essentially, the run-time components of any libraries that 73 are used by programs in <filename class="directory">/bin</filename> or 74 <filename class="directory">/sbin</filename> should reside in 75 <filename class="directory">/lib</filename> so that they are on the root 76 partition and available in the event of 77 <filename class="directory">/usr</filename> being inaccessible.</para> 69 <para>It is good policy and common practice to place important 70 libraries into the <filename class="directory">/lib</filename> 71 directory. This is most important in scenarios where <filename 72 class="directory">/usr</filename> is on a separate partition. 73 Essentially, the run-time components of any libraries that are used by 74 programs in <filename class="directory">/bin</filename> or <filename 75 class="directory">/sbin</filename> should reside in <filename 76 class="directory">/lib</filename> so that they are on the root 77 partition and available in the event of <filename 78 class="directory">/usr</filename> being inaccessible.</para> 78 79 79 <para>For the above reason wemove the run-time components of the shared Zlib80 <para>For the above reason, move the run-time components of the shared Zlib 80 81 into <filename class="directory">/lib</filename>:</para> 81 82 82 83 <screen><userinput>mv /usr/lib/libz.so.* /lib</userinput></screen> 83 84 84 <para> Now we need to fix the <filename class="symlink">/usr/lib/libz.so</filename> symlink85 because we just moved the file it points to:</para>85 <para>Fix the <filename class="symlink">/usr/lib/libz.so</filename> symlink 86 after the above move:</para> 86 87 87 88 <screen><userinput>ln -sf ../../lib/libz.so.1 /usr/lib/libz.so</userinput></screen> … … 112 113 113 114 </sect1> 115
Note:
See TracChangeset
for help on using the changeset viewer.