From 22b91d7fc47b9667453d56a23eac2b2f7afe9b57 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Sun, 9 Nov 2008 17:19:14 +0000 Subject: fix validation problem. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@58938 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/GettingStarted.html | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) (limited to 'docs/GettingStarted.html') diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index 9eccb19704..4f45d7e6e4 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -119,8 +119,7 @@ and performance.
  • cd where-you-want-the-C-front-end-to-live
  • gunzip --stdout llvm-gcc.platform.tar.gz | tar -xvf -
    • - +
  • Note: If the binary extension is ".bz" use bunzip2 instead of gunzip.
  • Add llvm-gcc's "bin" directory to your PATH variable.
    • @@ -320,10 +319,10 @@ project. future. We highly recommend that you rebuild your current binutils with the patch from Binutils bugzilla, if it wasn't already applied. -
  • XCode 2.5 and gcc 4.0.1 (Apple Build 5370) will trip +
  • XCode 2.5 and gcc 4.0.1 (Apple Build 5370) will trip internal LLVM assert messages when compiled for Release at optimization - levels greater than 0 (i.e., “-O1” and higher). - Add OPTIMIZE_OPTION="-O0" to the build command line + levels greater than 0 (i.e., "-O1" and higher). + Add OPTIMIZE_OPTION="-O0" to the build command line if compiling for LLVM Release or bootstrapping the LLVM toolchain.
    • -- cgit v1.2.3