cortesi		Wed Apr 17 13:35:57 2002 EDT

  Modified files:              
    /phpdoc/en/faq	build.xml 
  Log:
  adding consistency to the FAQ
  we dont usually use quotes around <command>  tags
  adding some docbook tags, where missin
  
  
Index: phpdoc/en/faq/build.xml
diff -u phpdoc/en/faq/build.xml:1.14 phpdoc/en/faq/build.xml:1.15
--- phpdoc/en/faq/build.xml:1.14	Thu Feb 28 13:14:31 2002
+++ phpdoc/en/faq/build.xml	Wed Apr 17 13:35:57 2002
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?> 
-<!-- $Revision: 1.14 $ --> 
+<!-- $Revision: 1.15 $ --> 
 <chapter id="faq.build"> 
   <title> Build Problems</title>
   <titleabbrev> Build Problems</titleabbrev>
@@ -20,15 +20,15 @@
     <answer> 
      <para> 
       You have to have the GNU autoconf package installed so you can
-      generate the configure script from configure.in. Just run
+      generate the configure script from <filename> configure.in</filename>. Just run
       <command> ./buildconf</command> in the top-level directory after getting
       the sources from the CVS server. (Also, unless you run configure
       with the <literal> --enable-maintainer-mode</literal> option, the
       configure script will not automatically get rebuilt when the
-      configure.in file is updated, so you should make sure to do that
+      <filename> configure.in</filename> file is updated, so you should make sure to do that
       manually when you notice configure.in has changed. One symptom
       of this is finding things like @VARIABLE@ in your Makefile after
-      configure or config.status is run.)
+      configure or <filename> config.status</filename> is run.)
      </para> 
     </answer> 
    </qandaentry> 
@@ -37,15 +37,15 @@
     <question> 
      <para> 
       I'm having problems configuring PHP to work with Apache. 
-      It says it can't find httpd.h, but it's right where I said it is!
+      It says it can't find <filename> httpd.h</filename>, but it's right where I said it is
!
      </para> 
     </question> 
     <answer> 
      <para> 
       You need to tell the configure/setup script the location of the
       top-level of your Apache source tree. This means that
-      you want to specify '<literal> --with-apache=/path/to/apache</literal>'
-      and <emphasis> not</emphasis> '<literal>--with-apache=/path/to/apache/src</literal>'.
+      you want to specify <literal> --with-apache=/path/to/apache</literal>
+      and <emphasis> not</emphasis> <literal>--with-apache=/path/to/apache/src</literal>.
      </para> 
     </answer> 
    </qandaentry> 
@@ -76,8 +76,8 @@
    <qandaentry id="faq.build.yytname"> 
     <question> 
      <para> 
-      When it is compiling the file language-parser.tab.c, it gives me errors 
-      that say 'yytname undeclared'.
+      When it is compiling the file <filename> language-parser.tab.c</filename>, it gives me
 errors 
+      that say <literal> yytname undeclared</literal>.
      </para> 
     </question> 
     <answer> 
@@ -91,7 +91,7 @@
    <qandaentry id="faq.build.link"> 
     <question> 
      <para> 
-      When I run 'make', it seems to run fine but then fails when it tries 
+      When I run <command> make</command>, it seems to run fine but then fails when it tries
 
       to link the final application complaining that it can't find some files.
      </para> 
     </question> 
@@ -99,8 +99,8 @@
      <para> 
       Some old versions of make that don't correctly put the compiled
       versions of the files in the functions directory into that same
-      directory. Try running "<command> cp *.o functions</command>" and then
-      re-running '<command> make</command>' to see if that helps. If it does, you should rea
lly
+      directory. Try running <command> cp *.o functions</command> and then
+      re-running <command> make</command> to see if that helps. If it does, you should reall
y
       upgrade to a recent version of GNU make.
      </para> 
     </answer> 
@@ -128,7 +128,7 @@
      </para> 
      <para> 
       Some people have also reported that they had to add '-ldl' immediately
-      following '<filename> libphp4.a</filename>' when linking with Apache.
+      following <filename> libphp4.a</filename> when linking with Apache.
      </para> 
     </answer> 
    </qandaentry> 
@@ -164,7 +164,7 @@
        </listitem> 
        <listitem> 
         <simpara> 
-         Type '<literal> make</literal>' followed by '<literal>make install</literal>'
+         Type <literal> make</literal> followed by <literal>make install</literal>
          to build PHP and copy the necessary files to the Apache distribution tree.
         </simpara> 
        </listitem> 
@@ -178,7 +178,7 @@
        </listitem> 
        <listitem> 
         <simpara> 
-         Type: '<command> ./Configure</command>' followed by '<literal>make</literal>'.
+         Type: <command> ./Configure</command> followed by <literal>make</literal>.
         </simpara> 
        </listitem> 
        <listitem> 
@@ -189,7 +189,7 @@
       </itemizedlist> 
      </para> 
      <para> 
-      <emphasis> Note:</emphasis> : You can also use the new Apache 
+      <emphasis> Note:</emphasis> You can also use the new Apache 
       <literal> ./configure</literal> script. See the instructions in 
       the <literal> README.configure</literal> file which is part of 
       your Apache distribution.  Also have a look at the <filename> INSTALL</filename> 
@@ -264,7 +264,7 @@
     </question> 
     <answer> 
      <para> 
-       Note that the libphp4.a file is not supposed to exist.  The
+       Note that the <filename> libphp4.a</filename> file is not supposed to exist.  The
        apache process will create it!
      </para> 
     </answer> 
@@ -298,8 +298,9 @@
       There are three things to check here.  First, for some reason
       when Apache builds the apxs Perl script, it sometimes ends up
       getting built without the proper compiler and flags variables.
-      Find your apxs script (try the command 'which apxs', 
-      it's sometimes found in /usr/local/apache/bin/apxs or /usr/sbin/apxs.
+      Find your apxs script (try the command <command> which apxs</command>, 
+      it's sometimes found in <filename> /usr/local/apache/bin/apxs</filename>
+      or <filename> /usr/sbin/apxs</filename>.
       Open it and check for lines similar to these:
       <programlisting> 
 my $CFG_CFLAGS_SHLIB  = '&nbsp;';          # substituted via Makefile.tmpl
@@ -323,8 +324,8 @@
       <programlisting> 
 my $CFG_LIBEXECDIR    = '/usr/lib/apache'; # substituted via APACI install
       </programlisting> 
-       Last, if you reconfigure/reinstall Apache, add a 'make clean' 
-       to the process after './configure' and before 'make'.
+       Last, if you reconfigure/reinstall Apache, add a <command> make clean</command> 
+       to the process after <command> ./configure</command> and before <command>make</comman
d> .
      </para> 
     </answer> 
    </qandaentry> 
@@ -332,12 +333,12 @@
    <qandaentry id="faq.build.microtime"> 
     <question> 
      <para> 
-     During 'make', I get errors in microtime, and a lot of 'RUSAGE_' stuff.
+     During <command> make</command>, I get errors in microtime, and a lot of <literal>RUSAG
E_</literal>  stuff.
     </para> 
     </question> 
     <answer> 
      <para> 
-      During the 'make' portion of installation, if you encounter problems 
+      During the <command> make</command> portion of installation, if you encounter problems
 
       that look similar to this:
       <programlisting> 
     microtime.c: In function `php_if_getrusage':
@@ -356,7 +357,7 @@
       </programlisting> 
      </para> 
      <para> 
-     Your system is broken.  You need to fix your /usr/include files by
+     Your system is broken.  You need to fix your <filename> /usr/include</filename> files b
y
      installing a glibc-devel package that matches your glibc.  This has
      absolutely nothing to do with PHP.  To prove this to yourself, try this
      simple test: