Commit 8b83d1b4 authored by John Criswell's avatar John Criswell
Browse files

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.

llvm-svn: 9454
parent 188c9510

llvm/docs/CFEBuildInstrs.html

+6 −3
Original line number Diff line number Diff line
@@ -15,9 +15,12 @@ 
C/C++ front-end, based on GCC 3.4, from source.</p>



<p><b>NOTE:</b> 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.</p>

process, and you should only try to do it if

<ul>

  <li>(A) you really, really, really can't use the binaries we distribute

  <li>(B) you need GCC to fix some of the header files on your system

  <li>(C) you are an elite GCC hacker.</p>

</ul>



<p>We welcome patches to help make this process simpler.</p>

llvm/docs/GettingStarted.html

+12 −0
Original line number Diff line number Diff line
@@ -407,6 +407,18 @@ 
    ./fixheaders

    </tt>



    <p>

    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.

    </p>



    <p>

    In cases like these, you may want to try

    <a href="CFEBuildInstrs.html">building the GCC front end from source.</a>

    This is not for the faint of heart, so be forewarned.

    </p>

    <!------------------------------------------------------------------------->

    <h3><a name="config">Local LLVM Configuration</a></h3>

    <!------------------------------------------------------------------------->