Fix an anchor.

[oota-llvm.git] / docs / TestingGuide.html

diff --git a/docs/TestingGuide.html b/docs/TestingGuide.html
index 2dd66d31c085537b7517ff72f84eae30802031ba..ac8e72bcb5e341c57111eb6c3970ec1dc5449b93 100644 (file)
--- a/docs/TestingGuide.html
+++ b/docs/TestingGuide.html
@@ -88,6 +88,12 @@ this route, you MUST specify all three components, and you need to only specify
 filenames themselves on the <tt>configure</tt> line.</li>
 </ul></dd>
 </dl>
+
+<p>Darwin (Mac OS X) developers can simplify the installation of Expect and tcl
+by using fink.  <tt>fink install expect</tt> will install both. Alternatively,
+Darwinports users can use <tt>sudo port install expect</tt> to install Expect
+and tcl.</p>
+
 </div>
 
 <!--=========================================================================-->
@@ -112,13 +118,17 @@ or<br>
 <pre>
 % gmake check
 </pre>
-<p>To run only a subdirectory of tests in llvm/test using DejaGNU (ie. Regression/Transforms). Just substitute the path to the subdirectory:</p>
+
+<p>To run only a subdirectory of tests in llvm/test using DejaGNU (ie.
+Regression/Transforms), just set the TESTSUITE variable to the path of the
+subdirectory (relative to <tt>llvm/test</tt>):</p>
 <pre>
 % gmake -C llvm/test TESTSUITE=Regression/Transforms
 </pre>
 
-<p><b>Note: If you are running the tests with <tt>objdir != subdir</tt> you must
-have run the complete testsuite before you can specify a subdirectory.</b></p>
+<p><b>Note: If you are running the tests with <tt>objdir != subdir</tt>, you
+must have run the complete testsuite before you can specify a
+subdirectory.</b></p>
 
 <p>To run the comprehensive test suite (tests that compile and execute whole 
 programs), run the <tt>llvm-test</tt> tests:</p>
@@ -141,8 +151,8 @@ programs), run the <tt>llvm-test</tt> tests:</p>
 
 <p>The LLVM test suite contains two major categories of tests: code
 fragments and whole programs. Code fragments are in the <tt>llvm</tt> module
-under the directory under the <tt>llvm/test</tt> directory. The whole programs
-test suite are in the <tt>llvm-test</tt> module under the main directory.</p>
+under the <tt>llvm/test</tt> directory. The whole programs
+test suite is in the <tt>llvm-test</tt> module under the main directory.</p>
 
 </div>
 
@@ -412,7 +422,7 @@ directory to run them.</p>
 <ol>
   <li>cd into the llvm/projects directory</li>
   <li>check out the <tt>llvm-test</tt> module with:<br/>
-  <tt>cvs -d :pserver:anon@llvm.cs.uiuc.edu:/var/cvs/llvm co -PR llvm-test</tt><br> 
+  <tt>cvs -d :pserver:anon@llvm.org:/var/cvs/llvm co -PR llvm-test</tt><br> 
   This will get the test suite into <tt>llvm/projects/llvm-test</tt></li>
   <li>configure the test suite. You can do this one of two ways:
   <ol>
@@ -464,7 +474,7 @@ will help you separate benign warnings from actual test failures.</p>
 <div class="doc_text">
 
 <p>
-The <a href="http://llvm.cs.uiuc.edu/testresults/">LLVM Nightly Testers</a>
+The <a href="http://llvm.org/testresults/">LLVM Nightly Testers</a>
 automatically check out an LLVM tree, build it, run the "nightly" 
 program test (described above), run  all of the feature and regression tests, 
 and then delete the checked out tree.  This tester is designed to ensure that 
@@ -488,7 +498,7 @@ The optimized x86 Linux nightly test is run from just such a script:</p>
 <pre>
 #!/bin/bash
 BASE=/proj/work/llvm/nightlytest
-export CVSROOT=:pserver:anon@llvm.cs.uiuc.edu:/var/cvs/llvm
+export CVSROOT=:pserver:anon@llvm.org:/var/cvs/llvm
 export BUILDDIR=$BASE/build 
 export WEBDIR=$BASE/testresults 
 export LLVMGCCDIR=/proj/work/llvm/cfrontend/install
@@ -517,7 +527,7 @@ we'll link your page to the global tester page.  Thanks!</p>
   src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
 
   John T. Criswell, Reid Spencer, and Tanya Lattner<br>
-  <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br/>
+  <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br/>
   Last modified: $Date$
 </address>
 </body>