Bootstrapping the 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.

Configure and build the LLVM libraries and tools using:

@@ -33,17 +39,17 @@ good GCC hacker.
     The use of the non-default target "tools-only" means that the
     LLVM tools and libraries will build, and the binaries will be
     deposited in llvm/tools/Debug, but the runtime (bytecode)
-    libraries will not build.
+    libraries will not build.

Add the directory containing the tools to your PATH.
```
- % set path = ( `cd llvm/tools/Debug && pwd` $path )
-
```
+ % set path = ( `cd llvm/tools/Debug && pwd` $path ) +
Unpack the C/C++ front-end source into cfrontend/src.
+
Unpack the C/C++ front-end source into cfrontend/src.
Edit src/configure. Change the first line (starting w/ #!) to - contain the correct full pathname of sh.
+ contain the correct full pathname of sh.
Make "build" and "install" directories as siblings of the "src" tree.
@@ -53,7 +59,7 @@ good GCC hacker.
% cd .. % mkdir build install % set CFEINSTALL = `pwd`/install - +

Configure, build and install the C front-end:

@@ -73,34 +79,36 @@ good GCC hacker.
   Fix 1: If you have system header files that include
    inline assembly, you may have to modify them to remove the inline
    assembly, and install the modified versions in
-   $CFEINSTALL/target-triplet/sys-include.
+   $CFEINSTALL/target-triplet/sys-include.
 
   Fix 2: If you are building the C++ front-end on a CPU we
    haven't tried yet, you will probably have to edit the appropriate
    version of atomicity.h under
    src/libstdc++-v3/config/cpu/name-of-cpu/atomicity.h
-   and apply a patch so that it does not use inline assembly.
+   and apply a patch so that it does not use inline assembly.