From cfaf80c471ac0e9bb646db582d70570340c6b413 Mon Sep 17 00:00:00 2001
From: Reid Spencer <rspencer@reidspencer.com>
Date: Wed, 22 Dec 2004 16:19:05 +0000
Subject: [PATCH] * Remove an unnecessary step. * Correct a path.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@19110 91177308-0d34-0410-b5e6-96231b3b80d8
---
 docs/CFEBuildInstrs.html | 10 +---------
 1 file changed, 1 insertion(+), 9 deletions(-)

diff --git a/docs/CFEBuildInstrs.html b/docs/CFEBuildInstrs.html
index ebcfa845eff..9f4b9d00b95 100644
--- a/docs/CFEBuildInstrs.html
+++ b/docs/CFEBuildInstrs.html
@@ -225,14 +225,6 @@ variable.</p>
 the same options as the last time. This will cause the configuration to now find
 the newly built llvm-gcc and llvm-g++ executables. </p></li>
 
-<li><p>If you edited header files during the C/C++ front-end build as
-described in "Fix 1" above, you must now copy those header files from
-<code>$CFEINSTALL/<i>target-triplet</i>/sys-include</code> to
-<code>$CFEINSTALL/lib/gcc/<i>target-triplet</i>/3.4-llvm/include</code>.
-(This should be the "include" directory in the same directory as the
-libgcc.a library, which you can find by running
-<code>$CFEINSTALL/bin/llvm-gcc --print-libgcc-file-name</code>.)</p></li>
-
 <li><p>Rebuild your CVS tree.  This shouldn't cause the whole thing to be
   rebuilt, but it should build the runtime libraries.  After the tree is
   built, install the runtime libraries into your GCC front-end build tree.
@@ -251,7 +243,7 @@ link times. Use the <tt>llvm-ranlib</tt> tool to do this, as follows:</p>
  % llvm-ranlib libiberty.a
  % llvm-ranlib libstdc++.a
  % llvm-ranlib libsupc++.a
- % cd $CFEINSTALL/lib/<i>target-triplet</i>/3.4-llvm
+ % cd $CFEINSTALL/lib/gcc/<i>target-triplet</i>/3.4-llvm
  % llvm-ranlib libgcc.a
  % llvm-ranlib libgcov.a
 </pre>