From: Misha Brukman
Date: Tue, 28 Oct 2003 21:09:29 +0000 (+0000)
Subject: * Put LLVM in title of page so readers know which CFE we're talking about
X-Git-Url: http://plrg.eecs.uci.edu/git/?p=oota-llvm.git;a=commitdiff_plain;h=b9e578934f903ff9bec7b19f9592a76f378ff0f7
* Put LLVM in title of page so readers know which CFE we're talking about
* Use instead of
if we're gonna number the list items
* Close
tags
* Stylize the document footer to be consistent
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@9558 91177308-0d34-0410-b5e6-96231b3b80d8
---
diff --git a/docs/CFEBuildInstrs.html b/docs/CFEBuildInstrs.html
index 5e753ab9925..588aef84494 100644
--- a/docs/CFEBuildInstrs.html
+++ b/docs/CFEBuildInstrs.html
@@ -3,24 +3,25 @@
- Bootstrapping the C/C++ Front-End
+ Bootstrapping the LLVM C/C++ Front-End
- Bootstrapping the C/C++ Front-End
+ Bootstrapping the LLVM C/C++ Front-End
This document is intended to explain the process of building the LLVM
C/C++ front-end, based on GCC 3.4, from source.
NOTE: This is currently a somewhat fragile, error-prone
-process, and you should only try to do it if
-
-
(A) you really, really, really can't use the binaries we distribute
-
(B) you need GCC to fix some of the header files on your system
-
(C) you are an elite GCC hacker.
-
+process, and you should only try to do it if:
+
+
+
you really, really, really can't use the binaries we distribute
+
you need GCC to fix some of the header files on your system
+
you are an elite GCC hacker.
+
We welcome patches to help make this process simpler.