From bcb38cf5e9b1be9d3e76099e7e3bddb8e07d15b2 Mon Sep 17 00:00:00 2001
From: Chris Lattner <sabre@nondot.org>
Date: Wed, 14 Feb 2007 07:33:00 +0000
Subject: [PATCH] There is no circular dependency between llvm and llvm-gcc
 anymore. stop scaring users.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34270 91177308-0d34-0410-b5e6-96231b3b80d8
---
 docs/GettingStarted.html | 17 +++++++++++++----
 1 file changed, 13 insertions(+), 4 deletions(-)

diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html
index 3684e4a6558..e7274210613 100644
--- a/docs/GettingStarted.html
+++ b/docs/GettingStarted.html
@@ -730,10 +730,11 @@ instructions</a> to successfully build the LLVM GCC front-end.</p>
 
 <div class="doc_text">
 
-<p>Before configuring and compiling the LLVM suite, you need to extract the LLVM
-GCC front end from the binary distribution.  It is used for building the
-bytecode libraries later used by the GCC front end for linking programs, and its
-location must be specified when the LLVM suite is configured.</p>
+<p>Before configuring and compiling the LLVM suite, you can optionally extract the 
+LLVM GCC front end from the binary distribution.  It is used for running the 
+llvm-test testsuite and for compiling C/C++ programs.  Note that you can optionally
+<a href="CFEBuildInstrs.html">build llvm-gcc yourself</a> after building the
+main LLVM repository.</p>
 
 <p>To install the GCC front end, do the following:</p>
 
@@ -743,6 +744,14 @@ location must be specified when the LLVM suite is configured.</p>
       -</tt></li>
 </ol>
 
+<p>Once the binary is uncompressed, you should add a symlink for llvm-gcc and 
+llvm-g++ to some directory in your path.  When you configure LLVM, it will 
+automatically detect llvm-gcc's presence (if it is in your path) enabling its
+use in llvm-test.  Note that you can always build or install llvm-gcc at any
+pointer after building the main LLVM repository: just reconfigure llvm and 
+llvm-test will pick it up.
+</p>
+
 <p>The binary versions of the GCC front end may not suit all of your needs.  For
 example, the binary distribution may include an old version of a system header
 file, not "fix" a header file that needs to be fixed for GCC, or it may be