From 0a1f67acfca8007c1c39f7b8b82fc786ca176d5e Mon Sep 17 00:00:00 2001 From: John Criswell Date: Thu, 23 Oct 2003 22:15:14 +0000 Subject: Added information on why someone would want to build the GCC front end. Added a link to this information from the Getting Started Guide. Changed the word "wicked" to "elite." The original sounds much cooler, but I fear the PR police when I take off my tinfoil hat. git-svn-id: https://llvm.org/svn/llvm-project/llvm/branches/release_1@9454 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/CFEBuildInstrs.html | 9 ++++++--- docs/GettingStarted.html | 12 ++++++++++++ 2 files changed, 18 insertions(+), 3 deletions(-) diff --git a/docs/CFEBuildInstrs.html b/docs/CFEBuildInstrs.html index 0f2c6c3b59..44c3c54d02 100644 --- a/docs/CFEBuildInstrs.html +++ b/docs/CFEBuildInstrs.html @@ -15,9 +15,12 @@ C/C++ front-end, based on GCC 3.4, from source.

NOTE: This is currently a somewhat fragile, error-prone -process, and you should only try to do it if (A) you really, really, -really can't use the binaries we distribute, and (B) you are a wicked -good GCC hacker.

+process, and you should only try to do it if +

We welcome patches to help make this process simpler.

diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index ddad3c26f5..6cd18723fc 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -407,6 +407,18 @@ ./fixheaders +

+ The binary versions of the 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. + This is not for the faint of heart, so be forewarned. +

Local LLVM Configuration

-- cgit v1.2.3-18-g5258