This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
XHTML compliance patches (gcc-3.0/)
- From: Andrea 'Fyre Wyzard' Bocci <fwyzard at inwind dot it>
- To: gcc-patches at gcc dot gnu dot org
- Cc: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Sat, 16 Feb 2002 02:27:38 +0100
- Subject: XHTML compliance patches (gcc-3.0/)
Et voila !
Index: gcc-3.0/buildstat.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/gcc-3.0/buildstat.html,v
retrieving revision 1.102
diff -u -3 -p -r1.102 buildstat.html
--- gcc-3.0/buildstat.html 11 Feb 2002 21:37:51 -0000 1.102
+++ gcc-3.0/buildstat.html 16 Feb 2002 01:18:18 -0000
@@ -460,7 +460,7 @@ Successful with modifications:
<td>i686-pc-linux-gnu (C3)</td>
<td>Red Hat 6.2, glibc 2.1.3, kernel 2.2.19</td>
<td>Successful:
-<a href="http://gcc.gnu.org/ml/gcc/2002-01/msg01314.html";>3.0.3</a></ltd>
+<a href="http://gcc.gnu.org/ml/gcc/2002-01/msg01314.html";>3.0.3</a></td>
</tr>
<tr>
Index: gcc-3.0/c99status.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/gcc-3.0/c99status.html,v
retrieving revision 1.3
diff -u -3 -p -r1.3 c99status.html
--- gcc-3.0/c99status.html 25 May 2001 19:38:34 -0000 1.3
+++ gcc-3.0/c99status.html 16 Feb 2002 01:18:18 -0000
@@ -20,9 +20,9 @@ paragraph 6) do not count as library iss
href="../c99status.html">C99 support in mainline CVS GCC</a> is also
available.</p>
-<p>See below the table for further notes on some issues.
+<p>See below the table for further notes on some issues.</p>
-<table border>
+<table border="1">
<tr><th>Feature</th>
<th>Library Issue</th>
<th>Done</th>
@@ -31,13 +31,13 @@ available.</p>
</tr>
<tr><td><em>restricted character set support via digraphs and
- <br><code><iso646.h></code> (originally specified in AMD1)</em></td>
+ <br /><code><iso646.h></code> (originally specified in AMD1)</em></td>
<td></td>
<td>Done</td><td></td><td></td>
</tr>
<tr><td><em>wide character library support in
- <code><wchar.h></code><br>and <code><wctype.h></code>
+ <code><wchar.h></code><br />and <code><wctype.h></code>
(originally specified in AMD1)</em></td>
<td>Library Issue</td>
<td></td><td></td><td>Missing</td>
@@ -62,7 +62,7 @@ available.</p>
<td></td><td>Done</td><td></td><td></td>
</tr>
-<tr><td><em><code>static</code> and type qualifiers<br>in parameter array declarators</em></td>
+<tr><td><em><code>static</code> and type qualifiers<br />in parameter array declarators</em></td>
<td></td><td></td><td></td><td>Missing</td>
</tr>
@@ -86,7 +86,7 @@ available.</p>
<td></td><td></td>
</tr>
-<tr><td><em>additional floating-point characteristics<br>in <code><float.h></code></em></td>
+<tr><td><em>additional floating-point characteristics<br />in <code><float.h></code></em></td>
<td></td><td>Done</td>
<td></td><td></td>
</tr>
@@ -109,7 +109,7 @@ available.</p>
</tr>
<tr><td><em>hexadecimal floating-point constants and
- <code>%a</code><br> and <code>%A</code>
+ <code>%a</code><br /> and <code>%A</code>
<code>printf</code>/<code>scanf</code> conversion specifiers</em></td>
<td>Library Issue</td><td>Done</td>
<td></td><td></td>
@@ -145,7 +145,7 @@ available.</p>
<td></td><td></td>
</tr>
-<tr><td><em>preprocessor arithmetic<br>done in <code>intmax_t</code>/<code>uintmax_t</code></em></td>
+<tr><td><em>preprocessor arithmetic<br />done in <code>intmax_t</code>/<code>uintmax_t</code></em></td>
<td></td><td></td><td>Broken</td><td></td>
</tr>
@@ -153,7 +153,7 @@ available.</p>
<td></td><td>Done</td><td></td><td></td>
</tr>
-<tr><td><em>new block scopes for selection<br>and iteration statements</em></td>
+<tr><td><em>new block scopes for selection<br />and iteration statements</em></td>
<td></td><td>Done</td><td></td><td></td>
</tr>
@@ -171,7 +171,7 @@ available.</p>
</tr>
<tr><td><em>the <code>vscanf</code> family of functions
- in<br><code><stdio.h></code> and <code><wchar.h></code></em></td>
+ in<br /><code><stdio.h></code> and <code><wchar.h></code></em></td>
<td>Library Issue</td>
<td>Done</td><td></td><td></td>
</tr>
@@ -181,12 +181,12 @@ available.</p>
<td></td><td></td><td>Missing</td>
</tr>
-<tr><td><em>floating-point environment access<br>in <code><fenv.h></code></em></td>
+<tr><td><em>floating-point environment access<br />in <code><fenv.h></code></em></td>
<td>Library Issue</td>
<td></td><td></td><td></td>
</tr>
-<tr><td><em>IEC 60559 (also known as<br>IEC 559 or IEEE arithmetic) support</em></td>
+<tr><td><em>IEC 60559 (also known as<br />IEC 559 or IEEE arithmetic) support</em></td>
<td></td><td></td><td>Broken</td><td></td>
</tr>
@@ -195,7 +195,7 @@ available.</p>
<td></td><td></td>
</tr>
-<tr><td><em><code>%lf</code> conversion specifier<br>allowed in <code>printf</code></em></td>
+<tr><td><em><code>%lf</code> conversion specifier<br />allowed in <code>printf</code></em></td>
<td>Library Issue</td><td>Done</td><td></td><td></td>
</tr>
@@ -222,7 +222,7 @@ available.</p>
<td></td><td>Done</td><td></td><td></td>
</tr>
-<tr><td><em>new struct type compatibility<br>rules (tag compatibility)</em></td>
+<tr><td><em>new struct type compatibility<br />rules (tag compatibility)</em></td>
<td></td><td>Done</td><td></td><td></td>
</tr>
@@ -251,12 +251,12 @@ available.</p>
<td>Library Issue</td><td>Done</td><td></td><td></td>
</tr>
-<tr><td><em>deprecate <code>ungetc</code> at the<br>beginning of a binary file</em></td>
+<tr><td><em>deprecate <code>ungetc</code> at the<br />beginning of a binary file</em></td>
<td>Library Issue</td>
<td></td><td></td><td></td>
</tr>
-<tr><td><em>remove deprecation of<br>aliased array parameters</em></td>
+<tr><td><em>remove deprecation of<br />aliased array parameters</em></td>
<td></td><td>Done</td>
<td></td><td></td>
</tr>
@@ -266,7 +266,7 @@ available.</p>
<td></td><td>Missing</td>
</tr>
-<tr><td><em>relaxed constraints on aggregate<br>and union initialization</em></td>
+<tr><td><em>relaxed constraints on aggregate<br />and union initialization</em></td>
<td></td><td>Done</td>
<td></td><td></td>
</tr>
@@ -277,7 +277,7 @@ available.</p>
</tr>
<tr><td><em><code>return</code> without expression not permitted
- in<br>function that returns a value (and vice versa)</em></td>
+ in<br />function that returns a value (and vice versa)</em></td>
<td></td><td>Done</td>
<td></td><td></td>
</tr>
Index: gcc-3.0/criteria.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/gcc-3.0/criteria.html,v
retrieving revision 1.27
diff -u -3 -p -r1.27 criteria.html
--- gcc-3.0/criteria.html 23 Jan 2002 15:42:27 -0000 1.27
+++ gcc-3.0/criteria.html 16 Feb 2002 01:18:18 -0000
@@ -39,7 +39,7 @@ possible.</p>
<p>GCC 3.0 will contain considerable improvements in functionality
relative to previous releases of GCC. Each of these improvements must
-be completed before GCC 3.0 is released:
+be completed before GCC 3.0 is released:</p>
<ul>
<li><p>C preprocessor</p>
<p>GCC 3.0 will use a new implementation of the C preprocessor.
@@ -50,38 +50,46 @@ be completed before GCC 3.0 is released:
based on <code>cpplib</code> rather than <code>cccp.c</code>.)
<strong>Done and surpassed</strong>. The integrated
preprocessor was ready in time to be made the default.</p>
+</li>
<li><p>C++ ABI</p>
<p>In order to avoid changing the C++ ABI from release to release,
as GCC has done to date, there must be a stable ABI.</p>
+</li>
<li><p>C++ Standard Library</p>
<p>The standard library is a part of the ABI. Changing the
standard library interfaces is effectively a change in the
ABI. It is important that we provide a standards-conforming
C++ standard library.</p>
+</li>
<li><p>Java Standard Library</p>
<p>The Java standard library should be present in the tree is
required in order to avoid users having to download it
separately. <strong>Done</strong>.</p>
+</li>
<li><p>GCC Support Library</p>
<p>The <code>libgcc</code> library will be built in both static
and shared library whenever <code>--enable-shared</code> is
used to configure GCC. As GCC 3.0 will contain other ABI
changes, now is as good a time as any to make this change.
<strong>Partly done</strong>.</p>
+</li>
<li><p>Java Front-End Garbage Collection</p>
<p>The Java front-end will be converted to use garbage collection,
like the other GCC front-ends. This conversion will enable the
simplification, optimization, and removal of code in the
machine-independent portions of the compiler, as well as in
the various back-ends. <strong>Done</strong>.</p>
+</li>
<li><p>Chill Front-End Garbage Collection</p>
<p>Like the Java front-end, the Chill front-end will be converted
to use garbage collection. <strong>Dropped</strong>. No
volunteer has been found to do this, so GCC 3.0 will not
support Chill unless one comes forward.</p>
+</li>
<li><p>Open Bugs</p>
<p>High-priority open bugs in GNATs will be fixed before the
GCC 3.0 release.</p>
+</li>
<li><p>Installation Documentation</p>
<p>Merge on-line installation documentation,
<code>gcc/install.texi</code>, past changes
@@ -91,6 +99,7 @@ be completed before GCC 3.0 is released:
<code>gcc/README.*</code> files, and
<code>gcc/f/g77install.texi</code>.
<strong>Partly done</strong></p>
+</li>
</ul>
<h2>Platform Support</h2>
@@ -104,14 +113,14 @@ possible, the release will support other
<table align="center">
<caption>Primary Evaluation Platforms</caption>
-<tr><th>Chip <th>OS <th>Triplet
-<tr><td>Alpha <td>RedHat Linux 6.2 <td>
-<tr><td>HPPA <td>HPUX 11.0 <td>hppa2.0w-hp-hpux11.00
-<tr><td>Intel x86<td>Debian GNU/Linux 2.2<td>i386-pc-linux-gnu
-<tr><td>Intel x86<td>RedHat Linux 6.2 <td>i686-pc-linux-gnu
-<tr><td>MIPS <td>IRIX 6.5 <td>mips-sgi-irix6.5
-<tr><td>PowerPC <td>AIX 4.3.3 <td>powerpc-ibm-aix4.3.3.0
-<tr><td>SPARC <td>Solaris 2.7 <td>sparc-sun-solaris2.7
+<tr><th>Chip</th> <th>OS</th> <th>Triplet</th></tr>
+<tr><td>Alpha</td> <td>RedHat Linux 6.2</td> <td></td></tr>
+<tr><td>HPPA</td> <td>HPUX 11.0</td> <td>hppa2.0w-hp-hpux11.00</td></tr>
+<tr><td>Intel x86</td><td>Debian GNU/Linux 2.2</td><td>i386-pc-linux-gnu</td></tr>
+<tr><td>Intel x86</td><td>RedHat Linux 6.2</td> <td>i686-pc-linux-gnu</td></tr>
+<tr><td>MIPS</td> <td>IRIX 6.5</td> <td>mips-sgi-irix6.5</td></tr>
+<tr><td>PowerPC</td> <td>AIX 4.3.3</td> <td>powerpc-ibm-aix4.3.3.0</td></tr>
+<tr><td>SPARC</td> <td>Solaris 2.7</td> <td>sparc-sun-solaris2.7</td></tr>
</table>
<p>GCC's performance on the following platforms will not be required
@@ -141,16 +150,16 @@ answering questions and reviewing patche
<table align="center">
<caption>Secondary Evaluation Platforms</caption>
-<tr><th>Chip <th>OS <th>Triplet
- <th>Tester
-<tr><td>Intel x86<td>FreeBSD 4.2 <td>i386-unknown-freebsd4.2
- <td><a href="mailto:obrien@freebsd.org";>David O'Brien</a></td>
-<tr><td>PowerPC <td>GNU/Linux <td>
-<tr><td>SPARC <td>SunOS 4.1.4 <td>sparc-sun-sunos4.1.4
-<tr><td>SPARC <td>Debian GNU/Linux 2.2<td>sparc-linux
- <td><a href="mailto:bcollins@debian.org";>Ben Collins</a>
-<tr><td>ARM <td>GNU/Linux <td>armv4l-unknown-linux-gnu
-<tr><td>Intel x86<td>Cygwin <td>i686-pc-cygwin
+<tr><th>Chip</th> <th>OS</th> <th>Triplet</th>
+ <th>Tester</th></tr>
+<tr><td>Intel x86</td><td>FreeBSD 4.2</td> <td>i386-unknown-freebsd4.2</td>
+ <td><a href="mailto:obrien@freebsd.org";>David O'Brien</a></td></tr>
+<tr><td>PowerPC</td> <td>GNU/Linux</td> <td></td></tr>
+<tr><td>SPARC</td> <td>SunOS 4.1.4</td> <td>sparc-sun-sunos4.1.4</td></tr>
+<tr><td>SPARC</td> <td>Debian GNU/Linux 2.2</td><td>sparc-linux</td>
+ <td><a href="mailto:bcollins@debian.org";>Ben Collins</a></td></tr>
+<tr><td>ARM</td> <td>GNU/Linux</td> <td>armv4l-unknown-linux-gnu</td></tr>
+<tr><td>Intel x86</td><td>Cygwin</td> <td>i686-pc-cygwin</td></tr>
</table>
<h2>Language Support</h2>
@@ -159,9 +168,9 @@ answering questions and reviewing patche
this release, only the behavior of front-ends for the following
languages will be considered part of the release criteria:</p>
<ul>
-<li>C
-<li>C++
-<li>Fortran
+<li>C</li>
+<li>C++</li>
+<li>Fortran</li>
</ul>
<p>The following languages will be supported by the release, but their
@@ -169,9 +178,9 @@ behavior will not be a primary considera
not to ship a particular release candidate:</p>
<ul>
-<li>Chill (<strong>Dropped</strong>; see above)
-<li>Java
-<li>Objective-C
+<li>Chill (<strong>Dropped</strong>; see above)</li>
+<li>Java</li>
+<li>Objective-C</li>
</ul>
<p>In particular, no application testing, code quality, or compile-time
@@ -205,30 +214,34 @@ different programming languages.</p>
<table align="center">
<caption>Integration Tests</caption>
-<tr><th>Name
- <th>Language
- <th>Version
- <th>Source URL
-<tr><td><a href="http://www.kernel.org";>Linux kernel</a>
- <td>C
- <td>2.4.0
+<tr><th>Name</th>
+ <th>Language</th>
+ <th>Version</th>
+ <th>Source URL</th>
+</tr>
+<tr><td><a href="http://www.kernel.org";>Linux kernel</a></td>
+ <td>C</td>
+ <td>2.4.0</td>
<td><a
href="ftp://ftp.kernel.org/pub/linux/kernel/v2.4/linux-2.4.0.tar.gz";>
- linux-2.4.0.tar.gz</a>
-<tr><td><a href="http://www.gnu.org/software/emacs/";>GNU Emacs</a>
- <td>C
- <td>20.6
- <td>
-<tr><td><a href="http://www.acl.lanl.gov/pooma/";>POOMA</a>
- <td>C++
- <td>2.2.0
+ linux-2.4.0.tar.gz</a></td>
+</tr>
+<tr><td><a href="http://www.gnu.org/software/emacs/";>GNU Emacs</a></td>
+ <td>C</td>
+ <td>20.6</td>
+ <td></td>
+</tr>
+<tr><td><a href="http://www.acl.lanl.gov/pooma/";>POOMA</a></td>
+ <td>C++</td>
+ <td>2.2.0</td>
<td><a href="http://www.acl.lanl.gov/distributions/pooma-2.3.0.tgz";>
- pooma-2.3.0.tgz</a>
-<tr><td><a href="http://www.netlib.org/lapack/index.html";>LAPACK</a>
- <td>Fortran
- <td>3.0
+ pooma-2.3.0.tgz</a></td>
+</tr>
+<tr><td><a href="http://www.netlib.org/lapack/index.html";>LAPACK</a></td>
+ <td>Fortran</td>
+ <td>3.0</td>
<td><a href="http://www.netlib.org/lapack/lapack.tgz";>
- LAPACK (testing programs)</a>
+ LAPACK (testing programs)</a></td>
</tr>
</table>
@@ -279,16 +292,20 @@ previous releases. Therefore, we will u
for measuring code quality:</p>
<table align="center">
-<tr><th align=left>Name</th>
- <th align=left>Language</th>
- <th align=left>Source URL</th>
+<tr><th align="left">Name</th>
+ <th align="left">Language</th>
+ <th align="left">Source URL</th>
+</tr>
<tr><td>gzip 1.2.4a</td><td>C</td>
+</tr>
<tr><td>Stepanov</td><td>C++</td>
<td><a href="ftp://ftp.kai.com/pub/benchmarks/stepanov_v1p2.C";>
stepanov_v1p2.C</a></td>
+</tr>
<tr><td>LAPACK</td><td>Fortran</td>
<td><a href="http://www.netlib.org/lapack/lapack.tgz";>
LAPACK 3.0 (timing programs)</a></td>
+</tr>
</table>
<p>A Java benchmark is not required for this release since there is
@@ -321,18 +338,22 @@ cost.</p>
<p>In order to measure compile-time performance, we will use the
following unit tests:</p>
<table>
-<tr><th align=left>Name
- <th align=left>Language
- <th align=left>Source
- <th align=left>Flags
- <th align=left>Comments
-<tr><td>insn-attrtab.c<td>C<td>
- <td>-O2
+<tr><th align="left">Name</th>
+ <th align="left">Language</th>
+ <th align="left">Source</th>
+ <th align="left">Flags</th>
+ <th align="left">Comments</th>
+</tr>
+<tr><td>insn-attrtab.c</td><td>C</td><td></td>
+ <td>-O2</td>
<td>This file contains a large machine-generated switch
statement; it is a reasonable benchmark for testing flow
- optimizations and for handling large functions.
-<tr><td><td>C++
-<tr><td><td>Fortran
+ optimizations and for handling large functions.</td>
+</tr>
+<tr><td></td><td>C++</td>
+</tr>
+<tr><td></td><td>Fortran</td>
+</tr>
</table>
<p>In addition to these unit tests, we will measure the time and peak
@@ -348,18 +369,18 @@ more than 25%, that candidate will be de
<p>The following issues are as of yet unresolved:</p>
<ul>
-<li>What integration tests should be used for Fortran?
+<li>What integration tests should be used for Fortran?</li>
<li>What other tests should we use for compile-time performance
-measurement?
-<li>What tests should we use for code quality?
-<li>Should <code>-fstrict-aliasing</code> be enabled?
+measurement?</li>
+<li>What tests should we use for code quality?</li>
+<li>Should <code>-fstrict-aliasing</code> be enabled?</li>
<li>Should we use flags higher than <code>-O2 -g</code> when
bootstrapping? (Probably we should have a matrix of various flags, as
-in previous releases.)
-<li>Should we add PowerPC GNU/Linux to the list of platforms?
-<li>Should we use Tru64 in place of Alpha GNU/Linux?
-<li>Should we eliminate setjmp/longjmp exception-handling?
-<li>Which open bugs need to be fixed?
+in previous releases.)</li>
+<li>Should we add PowerPC GNU/Linux to the list of platforms?</li>
+<li>Should we use Tru64 in place of Alpha GNU/Linux?</li>
+<li>Should we eliminate setjmp/longjmp exception-handling?</li>
+<li>Which open bugs need to be fixed?</li>
</ul>
</body>
Index: gcc-3.0/index.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/gcc-3.0/index.html,v
retrieving revision 1.7
diff -u -3 -p -r1.7 index.html
--- gcc-3.0/index.html 23 Jan 2002 15:42:27 -0000 1.7
+++ gcc-3.0/index.html 16 Feb 2002 01:18:18 -0000
@@ -13,7 +13,7 @@ October 25, 2001: GCC 3.0.2 has been rel
December 20, 2001: GCC 3.0.3 has been released.<br />
</p>
-<hr>
+<hr/>
<h1>GCC 3.0.3</h1>
Index: gcc-3.0/lapack-guide.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/gcc-3.0/lapack-guide.html,v
retrieving revision 1.4
diff -u -3 -p -r1.4 lapack-guide.html
--- gcc-3.0/lapack-guide.html 23 Jan 2002 15:42:27 -0000 1.4
+++ gcc-3.0/lapack-guide.html 16 Feb 2002 01:18:18 -0000
@@ -42,6 +42,7 @@ lapack.tgz</a>. This is a 5 Mb file.</p>
</ul>
Note that the value of RANLIB depends on ranlib being
available (and necessary) on your operating system.
+</li>
<li>If you want to test LAPACK with an uninstalled compiler,
change the following in the above:
<ul>
Index: gcc-3.0/libgcc.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/gcc-3.0/libgcc.html,v
retrieving revision 1.4
diff -u -3 -p -r1.4 libgcc.html
--- gcc-3.0/libgcc.html 23 Jan 2002 15:42:28 -0000 1.4
+++ gcc-3.0/libgcc.html 16 Feb 2002 01:18:18 -0000
@@ -17,26 +17,29 @@ static library. In addition this page d
<p>Richard Henderson provided an excellent summary of the issues in <a
href="http://gcc.gnu.org/ml/gcc/2000-04/msg00610.html";>a mail
message</a> posted to the GCC mailing lists. For maximum convenience,
-that message is paraphrased here:
+that message is paraphrased here:</p>
<ul>
<li>Shared objects must be linked against <code>libgcc</code>, just as
main programs must be, in order to provide a variety of run-time
support.
+</li>
<li>If two shared objects (or one shared object and a main program)
are linked against different versions of <code>libgcc</code> havoc
may ensue. In particular, entry points with the same name in
different versions of <code>libgcc</code> may operate in different
ways.
+</li>
<li>To this end, a shared library version of <code>libgcc</code>
should be persuaded. All shared objects, and programs linked
dynamically, should link against the shared version of
<code>libgcc</code>. That will ensure that only one version of
<code>libgcc</code> is present in any given program.
+</li>
</ul>
-<p>Unfortunately, there are negative consequences as well:
+<p>Unfortunately, there are negative consequences as well:</p>
<ul>
<li><p>The dynamic linker must be able to find <code>libgcc</code>.
If <code>libgcc</code> is not installed in <code>/lib</code>,
@@ -51,6 +54,7 @@ that message is paraphrased here:
language-specific run-time libraries; when created as shared
libraries, such libraries must be made available to the dynamic
linker.)</p>
+</li>
<li><p>The usual concerns about shared library versioning apply. A
program linked against <code>libgcc.1.2.so</code> may not work
@@ -63,6 +67,7 @@ that message is paraphrased here:
<code>libgcc</code> if the version of <code>libgcc</code> used
when compiling the program is newer than the version of
<code>libgcc</code> present on the target system.</p>
+</li>
</ul>
<h2>Conclusions</h2>
Index: gcc-3.0/pooma-guide.html
===================================================================
RCS file: /cvsroot/gcc/wwwdocs/htdocs/gcc-3.0/pooma-guide.html,v
retrieving revision 1.3
diff -u -3 -p -r1.3 pooma-guide.html
--- gcc-3.0/pooma-guide.html 23 Jan 2002 15:42:28 -0000 1.3
+++ gcc-3.0/pooma-guide.html 16 Feb 2002 01:18:18 -0000
@@ -48,6 +48,7 @@ programs, and run the examples, use</p>
<li>If unsuccessful, read the resulting tester.log log file and fix
the problem or email it to someone who can diagnose and fix the
problem.
+</li>
</ul>
<h2>Testing</h2>