X-Git-Url: http://plrg.eecs.uci.edu/git/?p=oota-llvm.git;a=blobdiff_plain;f=docs%2FCFEBuildInstrs.html;h=be844b9da895054c0f12190549a0acfc37b89735;hp=3dde111a5df2a1fdf222a414a641bf0655748309;hb=2998d3fde716816c1ac53675798af3bd5cf48fa8;hpb=46079d2274de38bd08ea7f731726d1a5a1296b75 diff --git a/docs/CFEBuildInstrs.html b/docs/CFEBuildInstrs.html index 3dde111a5df..be844b9da89 100644 --- a/docs/CFEBuildInstrs.html +++ b/docs/CFEBuildInstrs.html @@ -1,28 +1,57 @@ -Bootstrapping the C/C++ Front-End + + + + + Bootstrapping the LLVM C/C++ Front-End + + + +
+ Bootstrapping the LLVM C/C++ Front-End +
- -

Bootstrapping the C/C++ Front-End

+
    +
  1. A Cautionary Note +
  2. Instructions +
-

+
+

Written by Brian R. Gaeke

+
- -
-Instructions -
-

Common Problem 2: FIXME: Chris should add a section about - common problems porting to a new architecture, including changes you - might have to make to the gcc/gcc/config/name-of-cpu - directory. For example (expand these):

+

Porting to a new architecture: If you are porting the new front-end + to a new architecture, or compiling in a different configuration that we have + previously, there are probably several changes you will have to make to the GCC + target to get it to work correctly. These include:

+
  • Go back into the LLVM source tree proper. Edit Makefile.config to redefine LLVMGCCDIR to the full pathname of the $CFEINSTALL directory, which is the directory you just installed the C front-end into. (The ./configure script is likely to -have set this to a directory which does not exist on your system.)

    +have set this to a directory which does not exist on your system.)

  • 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 @@ -108,7 +174,7 @@ described in "Fix 1" above, you must now copy those header files from $CFEINSTALL/lib/gcc/target-triplet/3.4-llvm/include. (This should be the "include" directory in the same directory as the libgcc.a library, which you can find by running -$CFEINSTALL/bin/gcc --print-libgcc-file-name.)

    +$CFEINSTALL/bin/gcc --print-libgcc-file-name.)

  • Build and install the runtime (bytecode) libraries by running:

    @@ -116,25 +182,29 @@ libgcc.a library, which you can find by running
      % mkdir $CFEINSTALL/bytecode-libs
      % gmake -C runtime install
      % setenv LLVM_LIB_SEARCH_PATH $CFEINSTALL/bytecode-libs
    -
    +
  • Test the newly-installed C frontend by one or more of the following means:

    - -

    +

    +
  • + - - -
    -
    Brian Gaeke
    -Last modified: $Date$ -
    +
    + + +