linux-from-scratch/glfs
1
0
Fork 0
mirror of https://github.com/Zeckmathederg/glfs.git synced 2025-01-24 23:32:12 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Removed excess spaces from the ends of lines in the source files

Browse Source 
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@4508 af4574ff-66df-0310-9fd7-8a98e5e911e0
This commit is contained in:
Randy McMurchy 2005-05-30 21:38:32 +00:00
parent dae2ba0bed
commit 7cd76d6218
11 changed files with 143 additions and 143 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
general/prog/dejagnu.xml
View File

@ -29,8 +29,8 @@
<sect2 role="package">
<title>Introduction to DejaGnu</title>
<para><application>DejaGnu</application> is a framework for running test suites
on GNU tools. It is written in <command>expect</command>,
<para><application>DejaGnu</application> is a framework for running test suites
on GNU tools. It is written in <command>expect</command>,
which uses <application>Tcl</application> (Tool command language).</para>
<bridgehead renderas="sect3">Package Information</bridgehead>
@ -68,7 +68,7 @@
<sect2 role="installation">
<title>Installation of DejaGnu</title>
<para>Install <application>DejaGnu</application> by running the following
<para>Install <application>DejaGnu</application> by running the following
commands:</para>
<screen><userinput>./configure --prefix=/usr &amp;&amp;
@ -93,7 +93,7 @@ make install-doc</userinput></screen>
<seglistitem>
<seg>runtest</seg>
<seg>None</seg>
<seg>There are numerous <application>Expect</application> scripts installed in
<seg>There are numerous <application>Expect</application> scripts installed in
the <filename class='directory'>/usr/share/dejagnu</filename> hierarchy.</seg>
<seg>/usr/share/dejagnu</seg>
</seglistitem>
@ -107,7 +107,7 @@ make install-doc</userinput></screen>
<varlistentry id="runtest">
<term><command>runtest</command></term>
<listitem>
<para>is the <application>DejaGnu</application> test driver program. It is
<para>is the <application>DejaGnu</application> test driver program. It is
used to control what tests to run, and variations on how to run them.</para>
<indexterm zone="dejagnu runtest">
<primary sortas="b-runtest">runtest</primary>

74
general/prog/doxygen.xml
View File

@ -29,20 +29,20 @@
<sect2 role="package">
<title>Introduction to Doxygen</title>
<para>The <application>Doxygen</application> package contains a documentation
system for C++, C, Java, Objective-C, Corba IDL and to some extent PHP, C# and D.
This is useful for generating HTML documentation and/or an off-line reference manual
from a set of documented source files. There is also support for generating output in RTF,
PostScript, hyperlinked PDF, compressed HTML, and Unix man pages. The documentation
is extracted directly from the sources, which makes it much easier to keep the
<para>The <application>Doxygen</application> package contains a documentation
system for C++, C, Java, Objective-C, Corba IDL and to some extent PHP, C# and D.
This is useful for generating HTML documentation and/or an off-line reference manual
from a set of documented source files. There is also support for generating output in RTF,
PostScript, hyperlinked PDF, compressed HTML, and Unix man pages. The documentation
is extracted directly from the sources, which makes it much easier to keep the
documentation consistent with the source code.</para>
<para>You can also configure <application>Doxygen</application> to extract the
code structure from undocumented source files. This is very useful to quickly
find your way in large source distributions. Used along with
<application>GraphViz</application>, you can also visualize the relations
between the various elements by means of include dependency graphs,
inheritance diagrams, and collaboration diagrams, which are all generated
<para>You can also configure <application>Doxygen</application> to extract the
code structure from undocumented source files. This is very useful to quickly
find your way in large source distributions. Used along with
<application>GraphViz</application>, you can also visualize the relations
between the various elements by means of include dependency graphs,
inheritance diagrams, and collaboration diagrams, which are all generated
automatically.</para>
<bridgehead renderas="sect3">Package Information</bridgehead>
@ -70,10 +70,10 @@
<bridgehead renderas="sect3">Doxygen Dependencies</bridgehead>
<bridgehead renderas="sect4">Optional</bridgehead>
<para><xref linkend="qt"/>,
<xref linkend="python"/>,
<xref linkend="tex"/>,
<xref linkend="gs"/> or <xref linkend="espgs"/>, and
<para><xref linkend="qt"/>,
<xref linkend="python"/>,
<xref linkend="tex"/>,
<xref linkend="gs"/> or <xref linkend="espgs"/>, and
<ulink url="http://www.graphviz.org/">GraphViz</ulink></para>
</sect2>
@ -81,7 +81,7 @@
<sect2 role="installation">
<title>Installation of Doxygen</title>
<para>Install <application>Doxygen</application> by running the following
<para>Install <application>Doxygen</application> by running the following
commands:</para>
<screen><userinput>rm src/unistd.h &amp;&amp;
@ -92,10 +92,10 @@ make</userinput></screen>
<screen role="root"><userinput>make install</userinput></screen>
<para>If you wish to generate and install the package documentation (which
includes the man pages), ensure the <application>Python</application>,
<para>If you wish to generate and install the package documentation (which
includes the man pages), ensure the <application>Python</application>,
<application>TeX</application> and <application>GraphViz</application>
packages are installed, then substitute the following commands for the
packages are installed, then substitute the following commands for the
<command>make install</command> command above:</para>
<screen role="root"><userinput>make docs &amp;&amp;
@ -111,31 +111,31 @@ make install_docs</userinput></screen>
<sect2 role="commands">
<title>Command Explanations</title>
<para><command>rm src/unistd.h</command>: There is a bug in
<application>Flex</application>-2.5.31 which causes
<command>make</command> to use this file instead of the system
installed version. Removing this file allows the GUI front-end to build
<para><command>rm src/unistd.h</command>: There is a bug in
<application>Flex</application>-2.5.31 which causes
<command>make</command> to use this file instead of the system
installed version. Removing this file allows the GUI front-end to build
successfully.</para>
<para><option>--with-doxywizard</option>: Use this parameter if
<application>Qt</application> is installed and you wish to build the
<para><option>--with-doxywizard</option>: Use this parameter if
<application>Qt</application> is installed and you wish to build the
GUI front-end.</para>
<para><command>make docs</command>: This command builds the
<para><command>make docs</command>: This command builds the
man pages and HTML documentation.</para>
<para><command>make pdf</command>: This command builds a
<para><command>make pdf</command>: This command builds a
PDF version of the <application>Doxygen</application>
Manual.</para>
<para><command>install ...</command>: These commands install some files
<para><command>install ...</command>: These commands install some files
required by the documentation installation.</para>
<para><emphasis>Note: For documentation in a language other than English,
replace the <quote>_en</quote> with the country code of your
<para><emphasis>Note: For documentation in a language other than English,
replace the <quote>_en</quote> with the country code of your
locale.</emphasis></para>
<para><command>make install_docs</command>: This command installs
<para><command>make install_docs</command>: This command installs
the binaries and documentation.</para>
</sect2>
@ -163,9 +163,9 @@ make install_docs</userinput></screen>
<varlistentry id="doxygen-prog">
<term><command>doxygen</command></term>
<listitem>
<para>is a command-line based utility used to generate template
configuration files and then generate documentation from these templates. Use
<command>doxygen --help</command> for an explanation of the command-line
<para>is a command-line based utility used to generate template
configuration files and then generate documentation from these templates. Use
<command>doxygen --help</command> for an explanation of the command-line
parameters.</para>
<indexterm zone="doxygen doxygen-prog">
<primary sortas="b-doxygen">doxygen</primary>
@ -176,7 +176,7 @@ make install_docs</userinput></screen>
<varlistentry id="doxytag">
<term><command>doxytag</command></term>
<listitem>
<para>is used to generate a tag file and/or a search index for a set
<para>is used to generate a tag file and/or a search index for a set
of HTML files.</para>
<indexterm zone="doxygen doxytag">
<primary sortas="b-doxytag">doxytag</primary>
@ -187,7 +187,7 @@ make install_docs</userinput></screen>
<varlistentry id="doxywizard">
<term><command>doxywizard</command></term>
<listitem>
<para>is a GUI front-end for configuring and
<para>is a GUI front-end for configuring and
running <command>doxygen</command>.</para>
<indexterm zone="doxygen doxywizard">
<primary sortas="b-doxywizard">doxywizard</primary>

14
general/prog/gcc2.xml
View File

@ -45,11 +45,11 @@ url="&gcc2-download-ftp;"/></para></listitem>
<sect3><title>Additional downloads</title>
<itemizedlist spacing='compact'>
<listitem><para>Required Patch: <ulink
<listitem><para>Required Patch: <ulink
url="&patch-root;/gcc-&gcc2-version;-2.patch"/></para></listitem>
<listitem><para>Required Patch: <ulink
<listitem><para>Required Patch: <ulink
url="&patch-root;/gcc-&gcc2-version;-no_fixinc-1.patch"/></para></listitem>
<listitem><para>Required Patch: <ulink
<listitem><para>Required Patch: <ulink
url="&patch-root;/gcc-&gcc2-version;-returntype_fix-1.patch"/></para></listitem>
</itemizedlist>
</sect3>
@ -65,14 +65,14 @@ url="&patch-root;/gcc-&gcc2-version;-returntype_fix-1.patch"/></para></listitem>
patch -Np1 -i ../gcc-&gcc2-version;-no_fixinc-1.patch &amp;&amp;
patch -Np1 -i ../gcc-&gcc2-version;-returntype_fix-1.patch</command></userinput></screen>
<para>The <acronym>GCC</acronym> development team recommends building in a
<para>The <acronym>GCC</acronym> development team recommends building in a
separate directory.</para>
<screen><userinput><command>mkdir ../gcc-build &amp;&amp;
cd ../gcc-build</command></userinput></screen>
<para>Configure <acronym>GCC</acronym> to build the
<application>C</application> and <application>C++</application> compilers and
<application>C</application> and <application>C++</application> compilers and
enable the related <application>C++</application> options.</para>
<screen><userinput><command>../gcc-&gcc2-version;/configure \
@ -90,7 +90,7 @@ make install</command></userinput></screen>
<screen><userinput><command>L=`find /opt/gcc-&gcc2-version;/lib -name "*libstdc++*.so" -type f` &amp;&amp;
IL=`basename $L`</command></userinput></screen>
<para>Move the <application>C++</application> libraries to the standard lib
<para>Move the <application>C++</application> libraries to the standard lib
directory to avoid having to add <userinput>/opt/gcc-&gcc2-version;/lib
</userinput> to <filename>/etc/ld.so.conf</filename>.</para>
@ -121,7 +121,7 @@ compatibility links based on your requirements.</para>
<para>Whenever you need to use GCC-&gcc2-version; instead of your system
installed compiler, add
<filename class="directory">/opt/gcc-&gcc2-version;/bin</filename> to the
<filename class="directory">/opt/gcc-&gcc2-version;/bin</filename> to the
front of your <envar>PATH</envar> or (preferably) set the <envar>CC</envar>
environment variable before compiling the concerned package.</para>

50
general/prog/gcc3.xml
View File

@ -29,12 +29,12 @@
<sect2 role="package">
<title>Introduction to GCC-&gcc3-version;</title>
<para>The reason for installing
<application>GCC</application>-&gcc3-version; is that
<para>The reason for installing
<application>GCC</application>-&gcc3-version; is that
some BLFS packages (such as compiled <application>Java</application>
and <application>OpenOffice</application>) have not been updated to be
compilable by <application>GCC</application>-&gcc-version;. Additionally,
some pre-compiled packages may require the
and <application>OpenOffice</application>) have not been updated to be
compilable by <application>GCC</application>-&gcc-version;. Additionally,
some pre-compiled packages may require the
<application>GCC</application>-&gcc3-version; libraries.</para>
<bridgehead renderas="sect3">Package Information</bridgehead>
@ -62,11 +62,11 @@
<bridgehead renderas="sect3">Additional Downloads</bridgehead>
<itemizedlist spacing='compact'>
<listitem>
<para>Required patch: <ulink
<para>Required patch: <ulink
url="&patch-root;/gcc-&gcc3-version;-no_fixincludes-1.patch"/></para>
</listitem>
<listitem>
<para>Required patch: <ulink
<para>Required patch: <ulink
url="&patch-root;/gcc-&gcc3-version;-linkonce-1.patch"/></para>
</listitem>
</itemizedlist>
@ -79,7 +79,7 @@
<sect2 role="installation">
<title>Installation of GCC-&gcc3-version;</title>
<para>Install <application>GCC</application>-&gcc3-version; by running
<para>Install <application>GCC</application>-&gcc3-version; by running
the following commands:</para>
<screen><userinput>patch -Np1 -i ../gcc-&gcc3-version;-no_fixincludes-1.patch &amp;&amp;
@ -92,11 +92,11 @@ cd ../gcc-build &amp;&amp;
--enable-threads=posix &amp;&amp;
make bootstrap</userinput></screen>
<para>If desired, run the test suite using the following commands. The
<command>test_summary</command> commands create log files which can be
compared to known good results located at <ulink
<para>If desired, run the test suite using the following commands. The
<command>test_summary</command> commands create log files which can be
compared to known good results located at <ulink
url="http://linuxfromscratch.org/~randy/gcc-334-lfs-6.0-test_summary.log"/>
and <ulink
and <ulink
url="http://linuxfromscratch.org/~randy/gcc-334-lfs-6.0-test_summary_short.log"/>.</para>
<screen><userinput>make -k check &amp;&amp;
@ -118,20 +118,20 @@ chown -v -R root:root \
<sect2 role="commands">
<title>Command Explanations</title>
<para><command>mkdir ../gcc-build; cd ../gcc-build</command>: The
<application>GCC</application> development team recommends
<para><command>mkdir ../gcc-build; cd ../gcc-build</command>: The
<application>GCC</application> development team recommends
building in a separate directory.</para>
<para><parameter>--enable-shared --enable-languages=c,c++
--enable-threads=posix</parameter>: Configures
<application>GCC</application> to build the
<application>C</application> and <application>C++</application> compilers and
<para><parameter>--enable-shared --enable-languages=c,c++
--enable-threads=posix</parameter>: Configures
<application>GCC</application> to build the
<application>C</application> and <application>C++</application> compilers and
enable the related <application>C++</application> options.</para>
<para><command>mv -v /opt/gcc-&gcc3-version;/lib/libstdc++.so.5*
/usr/lib</command>: Moves the <application>C++</application> libraries to the
standard lib directory to avoid having to add
<userinput>/opt/gcc-&gcc3-version;/lib</userinput> to
<para><command>mv -v /opt/gcc-&gcc3-version;/lib/libstdc++.so.5*
/usr/lib</command>: Moves the <application>C++</application> libraries to the
standard lib directory to avoid having to add
<userinput>/opt/gcc-&gcc3-version;/lib</userinput> to
<filename>/etc/ld.so.conf</filename>.</para>
</sect2>
@ -149,7 +149,7 @@ chown -v -R root:root \
<para>Whenever you need to use GCC-&gcc3-version; instead of your system
installed compiler, add
<filename class="directory">/opt/gcc-&gcc3-version;/bin</filename> to the
<filename class="directory">/opt/gcc-&gcc3-version;/bin</filename> to the
front of your <envar>PATH</envar> or (preferably) set the <envar>CC</envar>
environment variable before compiling the concerned package.</para>
@ -166,9 +166,9 @@ chown -v -R root:root \
<segtitle>Installed Directories</segtitle>
<seglistitem>
<seg>c++, cpp, g++, gcc, gccbug, gcov, and architecture specific
<seg>c++, cpp, g++, gcc, gccbug, gcov, and architecture specific
names of these programs.</seg>
<seg>libgcc_s.so, libiberty.a, libstdc++.[a,so], libsupc++.a, and other
<seg>libgcc_s.so, libiberty.a, libstdc++.[a,so], libsupc++.a, and other
support libraries and files.</seg>
<seg>/opt/gcc-&gcc3-version;</seg>
</seglistitem>

24
general/prog/guile.xml
View File

@ -30,7 +30,7 @@
<title>Introduction to Guile</title>
<para>The <application>Guile</application> package contains the Project
GNU's extension language library. <application>Guile</application> also contains
GNU's extension language library. <application>Guile</application> also contains
a stand alone <application>Scheme</application> interpreter.</para>
<bridgehead renderas="sect3">Package Information</bridgehead>
@ -82,10 +82,10 @@ make</userinput></screen>
<seglistitem>
<seg>guile, guile-config, guile-snarf, and guile-tools</seg>
<seg>libguile.[so,a], libguilereadline-v-12.[so,a], libguile-ltdl.[so,a],
libguile-srfi-srfi-13-14-v-1.[so,a], libguile-srfi-srfi-4-v-1.[so,a], and
<seg>libguile.[so,a], libguilereadline-v-12.[so,a], libguile-ltdl.[so,a],
libguile-srfi-srfi-13-14-v-1.[so,a], libguile-srfi-srfi-4-v-1.[so,a], and
optionally, libqthreads.[so,a]</seg>
<seg>/usr/include/guile, /usr/include/guile-readline, /usr/include/libguile,
<seg>/usr/include/guile, /usr/include/guile-readline, /usr/include/libguile,
and /usr/share/guile</seg>
</seglistitem>
</segmentedlist>
@ -98,7 +98,7 @@ make</userinput></screen>
<varlistentry id="guile-prog">
<term><command>guile</command></term>
<listitem>
<para>is a stand-alone Scheme interpreter for
<para>is a stand-alone Scheme interpreter for
<application>Guile</application>.</para>
<indexterm zone="guile guile-prog">
<primary sortas="b-guile">guile</primary>
@ -109,9 +109,9 @@ make</userinput></screen>
<varlistentry id="guile-config">
<term><command>guile-config</command></term>
<listitem>
<para>is a <application>Guile</application> script which provides
the information necessary to link your programs against the
<application>Guile</application> library, in much the same way
<para>is a <application>Guile</application> script which provides
the information necessary to link your programs against the
<application>Guile</application> library, in much the same way
<xref linkend="pkgconfig"></xref> does.</para>
<indexterm zone="guile guile-config">
<primary sortas="b-guile-config">guile-config</primary>
@ -122,10 +122,10 @@ make</userinput></screen>
<varlistentry id="guile-snarf">
<term><command>guile-snarf</command></term>
<listitem>
<para>is a script to parse declarations in your
<para>is a script to parse declarations in your
<application>C</application> code for <application>Scheme</application>
visible <application>C</application> functions, i
<application>Scheme</application> objects to be used by
<application>Scheme</application> objects to be used by
<application>C</application> code, etc.</para>
<indexterm zone="guile guile-snarf">
<primary sortas="b-guile-snarf">guile-snarf</primary>
@ -136,8 +136,8 @@ make</userinput></screen>
<varlistentry id="guile-tools">
<term><command>guile-tools</command></term>
<listitem>
<para>is a wrapper program installed along with
<command>guile</command> which knows where a particular
<para>is a wrapper program installed along with
<command>guile</command> which knows where a particular
module is installed and calls it passing its args to a program.</para>
<indexterm zone="guile guile-tools">
<primary sortas="b-guile-tools">guile-tools</primary>

6
general/prog/librep.xml
View File

@ -61,8 +61,8 @@
<para><xref linkend="gdbm"/></para>
<bridgehead renderas="sect4">Optional</bridgehead>
<para><xref linkend="gmp"/> and
<xref linkend="gcc"/> (build Java so that
<para><xref linkend="gmp"/> and
<xref linkend="gcc"/> (build Java so that
<filename class='libraryfile'>libffi</filename> is built)</para>
</sect2>
@ -101,7 +101,7 @@ make</userinput></screen>
<seglistitem>
<seg>rep, rep-config, rep-remote, rep-xgettext, and repdoc</seg>
<seg>librep.so and numerous modules installed in the /usr/lib/rep
<seg>librep.so and numerous modules installed in the /usr/lib/rep
hierarchy</seg>
<seg>/usr/lib/rep, /usr/share/emacs/site-lisp, and /usr/share/rep</seg>
</seglistitem>

24
general/prog/nasm.xml
View File

@ -29,8 +29,8 @@
<sect2 role="package">
<title>Introduction to NASM</title>
<para><application>NASM</application> (Netwide Assembler)
is an 80x86 assembler designed for portability and modularity. It includes a
<para><application>NASM</application> (Netwide Assembler)
is an 80x86 assembler designed for portability and modularity. It includes a
disassembler as well.</para>
<bridgehead renderas="sect3">Package Information</bridgehead>
@ -58,7 +58,7 @@
<bridgehead renderas="sect3">NASM Dependencies</bridgehead>
<bridgehead renderas="sect4">Optional (for Building Documentation)</bridgehead>
<para><xref linkend="tex"/>, and
<para><xref linkend="tex"/>, and
<xref linkend="espgs"/> or <xref linkend="gs"/></para>
</sect2>
@ -66,7 +66,7 @@
<sect2 role="installation">
<title>Installation of NASM</title>
<para>Install <application>NASM</application> by running
<para>Install <application>NASM</application> by running
the following commands:</para>
<screen><userinput>./configure --prefix=/usr &amp;&amp;
@ -74,18 +74,18 @@ make &amp;&amp;
make -C rdoff/doc &amp;&amp;
make -C rdoff/doc html</userinput></screen>
<para>To build the base <application>NASM</application> documentation,
<para>To build the base <application>NASM</application> documentation,
ensure you have <application>Ghostscript</application> installed and issue:</para>
<screen><userinput>make doc</userinput></screen>
<para>To build the RDOFF Postscript documentation,
<para>To build the RDOFF Postscript documentation,
ensure you have <xref linkend="tex"/> installed and issue:</para>
<screen><userinput>sed -i -e "s/dvips \$&lt;/&amp; -o rdoff.ps/" rdoff/doc/Makefile &amp;&amp;
make -C rdoff/doc ps</userinput></screen>
<para>To build the RDOFF PDF documentation, ensure you have
<para>To build the RDOFF PDF documentation, ensure you have
<application>Ghostscript</application> installed and issue:</para>
<screen><userinput>make -C rdoff/doc pdf</userinput></screen>
@ -101,15 +101,15 @@ install -v -m755 -d /usr/share/doc/nasm/html &amp;&amp;
install -v -m644 rdoff/doc/v1-v2.txt /usr/share/doc/nasm &amp;&amp;
cp -v -R rdoff/doc/rdoff /usr/share/doc/nasm/html</userinput></screen>
<para>If you built the <application>Ghostscript</application> generated
documentation, install it using the following commands as the
<para>If you built the <application>Ghostscript</application> generated
documentation, install it using the following commands as the
<systemitem class="username">root</systemitem> user:</para>
<screen role="root"><userinput>make install_doc &amp;&amp;
install -v -m644 rdoff/doc/rdoff.pdf /usr/share/doc/nasm</userinput></screen>
<para>Lastly, if you built the RDOFF Postscript documentation, install it
using the following command as the
<para>Lastly, if you built the RDOFF Postscript documentation, install it
using the following command as the
<systemitem class="username">root</systemitem> user:</para>
<screen role="root"><userinput>install -v -m644 rdoff/doc/rdoff.ps /usr/share/doc/nasm</userinput></screen>
@ -125,7 +125,7 @@ install -v -m644 rdoff/doc/rdoff.pdf /usr/share/doc/nasm</userinput></screen>
<segtitle>Installed Directories</segtitle>
<seglistitem>
<seg>nasm, ndisasm, ldrdf, rdf2bin, rdf2com, rdf2ihx, rdfdump, rdflib, and
<seg>nasm, ndisasm, ldrdf, rdf2bin, rdf2com, rdf2ihx, rdfdump, rdflib, and
rdx</seg>
<seg>None</seg>
<seg>/usr/share/doc/nasm</seg>

26
general/prog/php.xml
View File

@ -29,8 +29,8 @@
<sect2 role="package">
<title>Introduction to PHP</title>
<para><application>PHP</application> is the PHP Hypertext Preprocessor.
Primarily used in dynamic web sites, it allows for programming code to be
<para><application>PHP</application> is the PHP Hypertext Preprocessor.
Primarily used in dynamic web sites, it allows for programming code to be
directly embedded into the HTML markup.</para>
<bridgehead renderas="sect3">Package Information</bridgehead>
@ -58,7 +58,7 @@
<bridgehead renderas="sect3">Additional Downloads</bridgehead>
<itemizedlist spacing="compact">
<listitem>
<para>Required patch for Berkeley DB: <ulink
<para>Required patch for Berkeley DB: <ulink
url="&patch-root;/php-&php-version;-db43-1.patch"/></para>
</listitem>
</itemizedlist>
@ -78,14 +78,14 @@
<xref linkend="curl"/>,
<ulink url="http://qdbm.sourceforge.net/">QDBM</ulink>,
<ulink url="http://cr.yp.to/cdb.html">cdb</ulink>,
<xref linkend="gdbm"/>,
<xref linkend="gdbm"/>,
<xref linkend="db"/>,
<xref linkend="fam"/>,
<ulink url="http://www.boutell.com/gd/">GD</ulink>,
<xref linkend="libpng"/>,
X (<xref linkend="xorg"/> or <xref linkend="xfree86"/>),
<xref linkend="freetype2"/>,
<ulink
<ulink
url="http://gd.tuwien.ac.at/visual/ibiblio/libs/graphics/t1lib-5.0.2.tar.gz">
t1lib</ulink>,
<xref linkend="gmp"/>
@ -132,7 +132,7 @@
server-side scripting as it is the most common form.</para>
</note>
<para>If you have <application>Berkeley DB</application> installed and
<para>If you have <application>Berkeley DB</application> installed and
wish to utilize it, apply the following patch:</para>
<screen><userinput>patch -Np1 -i ../php-&php-version;-db43-1.patch</userinput></screen>
@ -171,7 +171,7 @@ cp -v php.ini-recommended /etc/php.ini</userinput></screen>
<command>pear</command> will not be built.</para>
<note>
<para><application>PHP</application> has many more configure
<para><application>PHP</application> has many more configure
options that will enable support for certain things. You can use
<command>./configure --help</command> to see a full list of the
available options. Also, use of the
@ -205,17 +205,17 @@ cp -v php.ini-recommended /etc/php.ini</userinput></screen>
<para>To enable PHP support in the <application>Apache</application>
web server, a new LoadModule (which should be handled automatically by the
<command>make install</command> command) and AddType directives
<command>make install</command> command) and AddType directives
must be added to the <filename>httpd.conf</filename> file:</para>
<screen><literal>LoadModule php5_module lib/apache/libphp5.so
AddType application/x-httpd-php .php</literal></screen>
<para>Also, it can be useful to add an entry for
<filename>index.php</filename> to the DirectoryIndex directive of the
<para>Also, it can be useful to add an entry for
<filename>index.php</filename> to the DirectoryIndex directive of the
<filename>httpd.conf</filename> file.</para>
<para>You'll need to restart the <application>Apache</application> web server
<para>You'll need to restart the <application>Apache</application> web server
after making any modifications to the <filename>httpd.conf</filename>
file.</para>
@ -246,7 +246,7 @@ AddType application/x-httpd-php .php</literal></screen>
<varlistentry id="php-prog">
<term><command>php</command></term>
<listitem>
<para>is a command line interface that enables you to parse and
<para>is a command line interface that enables you to parse and
execute PHP code.</para>
<indexterm zone="php php-prog">
<primary sortas="b-php">php</primary>
@ -257,7 +257,7 @@ AddType application/x-httpd-php .php</literal></screen>
<varlistentry id="pear">
<term><command>pear</command></term>
<listitem>
<para>is the PHP Extension and Application
<para>is the PHP Extension and Application
Repository (PEAR) package manager.</para>
<indexterm zone="php pear">
<primary sortas="b-pear">pear</primary>

26
general/prog/python.xml
View File

@ -59,7 +59,7 @@
<bridgehead renderas="sect3">Additional Downloads</bridgehead>
<itemizedlist spacing='compact'>
<listitem>
<para>Required patch: <ulink
<para>Required patch: <ulink
url="&patch-root;/Python-&Python-version;-gdbm-1.patch"/></para>
</listitem>
</itemizedlist>
@ -68,7 +68,7 @@
<bridgehead renderas="sect4">Optional</bridgehead>
<para><xref linkend="openssl"/>,
<xref linkend="tk"/>,
<xref linkend="tk"/>,
<xref linkend="gdbm"/> and
<xref linkend="db"/></para>
@ -91,11 +91,11 @@ make</userinput></screen>
<screen role="root"><userinput>make install</userinput></screen>
<note>
<para>There is no documentation installed using the instructions above.
However, There are Latex sources included with the distribution. See the
<filename>Doc/README</filename> file in the source distribution for
instructions to format the LaTex sources. Alternatively, you can download
preformatted documentation from
<para>There is no documentation installed using the instructions above.
However, There are Latex sources included with the distribution. See the
<filename>Doc/README</filename> file in the source distribution for
instructions to format the LaTex sources. Alternatively, you can download
preformatted documentation from
<ulink url="http://www.python.org/doc/current/download.html"/>.</para>
</note>
@ -110,9 +110,9 @@ make</userinput></screen>
<segtitle>Installed Directories</segtitle>
<seglistitem>
<seg>pydoc, python, python2.4, smtpd.py, and optionally if
<seg>pydoc, python, python2.4, smtpd.py, and optionally if
<application>Tk</application> is installed, idle</seg>
<seg>libpython2.4.so and numerous modules installed in
<seg>libpython2.4.so and numerous modules installed in
/usr/lib/python2.4/lib-dynload</seg>
<seg>/usr/include/python2.4 and /usr/lib/python2.4</seg>
</seglistitem>
@ -126,7 +126,7 @@ make</userinput></screen>
<varlistentry id="idle">
<term><command>idle</command></term>
<listitem>
<para>is a wrapper script that opens a
<para>is a wrapper script that opens a
<application>Python</application> aware GUI editor.</para>
<indexterm zone="python idle">
<primary sortas="b-idle">idle</primary>
@ -137,7 +137,7 @@ make</userinput></screen>
<varlistentry id="pydoc">
<term><command>pydoc</command></term>
<listitem>
<para>is the <application>Python</application> documentation
<para>is the <application>Python</application> documentation
tool.</para>
<indexterm zone="python pydoc">
<primary sortas="b-pydoc">pydoc</primary>
@ -148,7 +148,7 @@ make</userinput></screen>
<varlistentry id="python-prog">
<term><command>python</command></term>
<listitem>
<para>is an interpreted, interactive, object-oriented programming
<para>is an interpreted, interactive, object-oriented programming
language.</para>
<indexterm zone="python python-prog">
<primary sortas="b-python">python</primary>
@ -170,7 +170,7 @@ make</userinput></screen>
<varlistentry id="smtpd.py">
<term><command>smtpd.py</command></term>
<listitem>
<para>is an SMTP proxy implemented in
<para>is an SMTP proxy implemented in
<application>Python</application>.</para>
<indexterm zone="python smtpd.py">
<primary sortas="b-smtpd.py">smtpd.py</primary>

24
general/prog/tcl.xml
View File

@ -29,7 +29,7 @@
<sect2 role="package">
<title>Introduction to Tcl</title>
<para>The <application>Tcl</application> package contains the Tool Command
<para>The <application>Tcl</application> package contains the Tool Command
Language, a robust general-purpose scripting language.</para>
<bridgehead renderas="sect3">Package Information</bridgehead>
@ -60,14 +60,14 @@
<title>Installation of Tcl</title>
<note>
<para>This package is also installed in LFS during
the bootstrap phase. The significant difference between the two installations
<para>This package is also installed in LFS during
the bootstrap phase. The significant difference between the two installations
(other than installing to <filename class="directory">/usr</filename>) is that
the package is installed in such a way that there is no need to keep the build
directory around after installation.</para>
</note>
<para>Install <application>Tcl</application> by running the following
<para>Install <application>Tcl</application> by running the following
commands:</para>
<screen><userinput>export VERSION=&tcl-version; &amp;&amp;
@ -95,7 +95,7 @@ ln -v -nsf ../../include/tcl${V} /usr/lib/tcl${V}/include &amp;&amp;
ln -v -sf libtcl${V}.so /usr/lib/libtcl.so &amp;&amp;
ln -v -sf tclsh${V} /usr/bin/tclsh</userinput></screen>
<para>Clean up the unprivileged user's environment using the following
<para>Clean up the unprivileged user's environment using the following
commands:</para>
<screen><userinput>unset VERSION &amp;&amp;
@ -104,9 +104,9 @@ unset DIR</userinput></screen>
<!--
<caution>
<para>If you build the package as an ordinary user and then switch to
root to install the package, ensure you set the environment variables
<envar>V</envar> and <envar>VERSION</envar> before running the installation
<para>If you build the package as an ordinary user and then switch to
root to install the package, ensure you set the environment variables
<envar>V</envar> and <envar>VERSION</envar> before running the installation
commands.</para>
</caution>
-->
@ -120,10 +120,10 @@ unset DIR</userinput></screen>
to build with thread support.</para>
<para><command>sed -i ...</command>: The <application>Tcl</application>
package assumes that the source that is used to build
<application>Tcl</application> is always kept around for compiling packages
that depend on <application>Tcl</application>. These <command>sed</command>s
remove the reference to the build directory and replace them by saner system
package assumes that the source that is used to build
<application>Tcl</application> is always kept around for compiling packages
that depend on <application>Tcl</application>. These <command>sed</command>s
remove the reference to the build directory and replace them by saner system
wide locations.</para>
<para><command>install ...</command>: These commands install the internal

8
general/prog/tk.xml
View File

@ -57,7 +57,7 @@
<bridgehead renderas="sect3">Tk Dependencies</bridgehead>
<bridgehead renderas="sect4">Required</bridgehead>
<para>X (<xref linkend="xfree86"/> or <xref linkend="xorg"/>) and
<para>X (<xref linkend="xfree86"/> or <xref linkend="xorg"/>) and
<xref linkend="tcl"/></para>
</sect2>
@ -65,7 +65,7 @@
<sect2 role="installation">
<title>Installation of Tk</title>
<para>Install <application>Tk</application> by running the following
<para>Install <application>Tk</application> by running the following
commands:</para>
<screen><userinput>export VERSION=&tk-version; &amp;&amp;
@ -77,7 +77,7 @@ make &amp;&amp;
sed -i "s:${DIR}/unix:/usr/lib:" tkConfig.sh &amp;&amp;
sed -i "s:${DIR}:/usr/include/tk${V}:" tkConfig.sh</userinput></screen>
<para>To test the results, issue: <command>make test</command>.
<para>To test the results, issue: <command>make test</command>.
Ensure you do it from an X Window display device with the
GLX extensions loaded, else the tests will hang.</para>
@ -102,7 +102,7 @@ unset DIR</userinput></screen>
<!--
<caution>
<para>If you build the package as an ordinary user and then switch to
<para>If you build the package as an ordinary user and then switch to
root to install the package, ensure you set the environment variables
<envar>V</envar> and <envar>VERSION</envar> before running the installation
commands.</para>