From: Chad Rosier Date: Sun, 26 Feb 2012 22:17:05 +0000 (+0000) Subject: Installing the GCC front end is no longer supported. X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=e342ec677326eba32c104f32a28b7230f7b24f50;p=oota-llvm.git Installing the GCC front end is no longer supported. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@151506 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index c4fd3a1459a..3495f87dc58 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -29,7 +29,6 @@
  • Unpacking the LLVM Archives
  • Checkout LLVM from Subversion
  • LLVM GIT mirror
    • -
  • Install the GCC Front End
  • Local LLVM Configuration
  • Compiling the LLVM Suite Source Code
  • Cross-Compiling LLVM
    • @@ -964,76 +963,6 @@ git svn rebase -l - -

    - Install the GCC Front End -

    - -
    - -

    Before configuring and compiling the LLVM suite (or if you want to use just the LLVM -GCC front end) you can optionally extract the front end from the binary distribution. -It is used for running the LLVM test-suite and for compiling C/C++ programs. Note that -you can optionally build llvm-gcc yourself after building the -main LLVM repository.

    - -

    To install the GCC front end, do the following (on Windows, use an archival tool -like 7-zip that understands gzipped tars):

    - -
      -
    1. cd where-you-want-the-front-end-to-live
      2. -
    2. gunzip --stdout llvm-gcc-4.2-version-platform.tar.gz | tar -xvf - -
      3. -
    - -

    Once the binary is uncompressed, if you're using a *nix-based system, add a symlink for -llvm-gcc and llvm-g++ to some directory in your path. If you're using a -Windows-based system, add the bin subdirectory of your front end installation directory -to your PATH environment variable. For example, if you uncompressed the binary to -c:\llvm-gcc, add c:\llvm-gcc\bin to your PATH.

    - -

    If you now want to build LLVM from source, when you configure LLVM, it will -automatically detect llvm-gcc's presence (if it is in your path) enabling its -use in test-suite. Note that you can always build or install llvm-gcc at any -point after building the main LLVM repository: just reconfigure llvm and -test-suite will pick it up. -

    - -

    As a convenience for Windows users, the front end binaries for MinGW/x86 include -versions of the required w32api and mingw-runtime binaries. The last remaining step for -Windows users is to simply uncompress the binary binutils package from -MinGW into your front end installation directory. While the -front end installation steps are not quite the same as a typical manual MinGW installation, -they should be similar enough to those who have previously installed MinGW on Windows systems.

    - -

    To install binutils on Windows:

    - -
      -
    1. download GNU Binutils from MinGW Downloads
      2. -
    2. cd where-you-uncompressed-the-front-end
      3. -
    3. uncompress archived binutils directories (not the tar file) into the current directory
      4. -
    - -

    The binary versions of the LLVM 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 linked with -libraries not available on your system. In cases like these, you may want to try -building the GCC front end from source. Thankfully, -this is much easier now than it was in the past.

    - -

    We also do not currently support updating of the GCC front end by manually overlaying -newer versions of the w32api and mingw-runtime binary packages that may become available -from MinGW. At this time, it's best to think of the MinGW LLVM GCC front end binary as -a self-contained convenience package that requires Windows users to simply download and -uncompress the GNU Binutils binary package from the MinGW project.

    - -

    Regardless of your platform, if you discover that installing the LLVM GCC front end -binaries is not as easy as previously described, or you would like to suggest improvements, -please let us know how you would like to see things improved by dropping us a note on our -mailing list.

    - -
    -

    Local LLVM Configuration @@ -1072,29 +1001,6 @@ script to configure the build system:

    The following options can be used to set or enable LLVM specific options:

    -
    --with-llvmgccdir
    -
    Path to the LLVM C/C++ FrontEnd to be used with this LLVM configuration. - The value of this option should specify the full pathname of the C/C++ Front - End to be used. If this option is not provided, the PATH will be searched for - a program named llvm-gcc and the C/C++ FrontEnd install directory will - be inferred from the path found. If the option is not given, and no llvm-gcc - can be found in the path then a warning will be produced by - configure indicating this situation. LLVM may still be built with - the tools-only target but attempting to build the runtime libraries - will fail as these libraries require llvm-gcc and llvm-g++. See - Install the GCC Front End for details on installing - the C/C++ Front End. See - Bootstrapping the LLVM C/C++ Front-End - for details on building the C/C++ Front End.
    -
    --with-tclinclude
    -
    Path to the tcl include directory under which tclsh can be - found. Use this if you have multiple tcl installations on your machine and you - want to use a specific one (8.x) for LLVM. LLVM only uses tcl for running the - dejagnu based test suite in llvm/test. If you don't specify this - option, the LLVM configure script will search for the tcl 8.4 and 8.3 - releases. -

    -
    --enable-optimized
    Enables optimized compilation (debugging symbols are removed