From: Chris Lattner Date: Tue, 11 Jul 2006 20:47:00 +0000 (+0000) Subject: Revamp this doc to be accurate w.r.t. building llvmgcc4 X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=810ad8c51c8ab471e85b3f6493b8829087f5afbc;p=oota-llvm.git Revamp this doc to be accurate w.r.t. building llvmgcc4 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@29113 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/CFEBuildInstrs.html b/docs/CFEBuildInstrs.html index c71d68b5358..fa49c29e0b8 100644 --- a/docs/CFEBuildInstrs.html +++ b/docs/CFEBuildInstrs.html @@ -19,7 +19,8 @@
  • Building under AIX
  • -
  • Instructions
  • +
  • llvm-gcc4 Instructions
  • +
  • llvm-gcc3 Instructions
  • License Information
  • @@ -36,9 +37,10 @@

    This document is intended to explain the process of building the -LLVM C/C++ front-end, based on GCC 3.4, from its source code. You -would have to do this, for example, if you are porting LLVM to a new -architecture or operating system.

    +LLVM C/C++ front-end from its source code. You have to do this, for example, if +you are porting LLVM to a new architecture or operating system, if you are +working from Top-Of-Tree CVS/SVN, or if there is no precompiled snapshot +available.

    NOTE: This is currently a somewhat fragile, error-prone process, and you should only try to do it if:

    @@ -71,7 +73,8 @@ and Settings" directory). We welcome patches to fix this issue. versions is incapable of compiling the LLVM GCC front-end correctly. If your Cygwin installation includes GCC 3.3.3, we strongly recommend that you download -GCC 3.4.3, build it separately, and use it for compiling the LLVM GCC front-end. This has been +GCC 3.4.3, build it separately, and use it for compiling the LLVM GCC front-end. + This has been shown to work correctly.

    Some versions of Cygwin utilize an experimental version of GNU binutils that will cause the GNU ld linker to fail an assertion when linking @@ -94,18 +97,24 @@ invalid code. Instead, use the system assembler and linker.

    -

    + +

    This section describes how to aquire and build llvm-gcc4, which is based on +the GCC 4.0.1 front-end. This front-end supports C, C++, Objective-C, and +Objective-C++. Note that the instructions for building this front-end are +completely different than those for building llvm-gcc3. +

    +
    1. Retrieve the appropriate llvm-gcc4-x.y.source.tar.gz archive from the llvm web site.

      It is also possible to download the sources of the llvm-gcc4 front end from -a read-only mirror using subversion. To check out the code the first time use; +a read-only mirror using subversion. To check out the code the first time use:

      svn co svn://anonsvn.opensource.apple.com/svn/llvm dst-directory @@ -117,6 +126,23 @@ a read-only mirror using subversion. To check out the code the first time use;

      The mirror is brought up to date every evening.

    2. + +
    3. Follow the directions in the top-level README.LLVM file for up-to-date + instructions on how to build llvm-gcc4.
    4. +
    +
    + + + + + +
    +
      +
    1. Aquire llvm-gcc3 from LLVM CVS or +from a release tarball.
    2. +
    3. Configure and build the LLVM libraries and tools. There are two ways to do this: either with objdir == srcdir or objdir != srcdir. It is recommended @@ -314,51 +340,8 @@ COPYING.LIB for more details.

      -The software also has the following additional copyrights: +More information is available in the FAQ.

      - -
      -
      -Copyright (c) 2003, 2004, 2005 University of Illinois at Urbana-Champaign.
      -All rights reserved.
      -
      -Developed by:
      -
      -    LLVM Team
      -
      -    University of Illinois at Urbana-Champaign
      -
      -    http://llvm.org
      -
      -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
      -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
      -FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE
      -CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
      -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
      -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS WITH THE
      -SOFTWARE.
      -
      -Copyright (c) 1994
      -Hewlett-Packard Company
      -
      -Permission to use, copy, modify, distribute and sell this software
      -and its documentation for any purpose is hereby granted without fee,
      -provided that the above copyright notice appear in all copies and
      -that both that copyright notice and this permission notice appear
      -in supporting documentation.  Hewlett-Packard Company makes no
      -representations about the suitability of this software for any
      -purpose.  It is provided "as is" without express or implied warranty.
      -
      -Copyright (c) 1996, 1997, 1998, 1999
      -Silicon Graphics Computer Systems, Inc.
      -
      -Permission to use, copy, modify, distribute and sell this software
      -and its documentation for any purpose is hereby granted without fee,
      -provided that the above copyright notice appear in all copies and
      -that both that copyright notice and this permission notice appear
      -in supporting documentation.  Silicon Graphics makes no
      -representations about the suitability of this software for any
      -purpose.  It is provided "as is" without express or implied warranty.