6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-11-02 07:11:49 +00:00
Code Issues Projects Releases Wiki Activity

There is no circular dependency between llvm and llvm-gcc anymore. stop

Browse Source 
scaring users.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34270 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Chris Lattner 2007-02-14 07:33:00 +00:00
parent 78bade278f
commit bcb38cf5e9
1 changed files with 13 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/GettingStarted.html
View File

@ -730,10 +730,11 @@ instructions</a> to successfully build the LLVM GCC front-end.</p>
<div class="doc_text"> <div class="doc_text">
<p>Before configuring and compiling the LLVM suite, you need to extract the LLVM <p>Before configuring and compiling the LLVM suite, you can optionally extract the
GCC front end from the binary distribution. It is used for building the LLVM GCC front end from the binary distribution. It is used for running the
bytecode libraries later used by the GCC front end for linking programs, and its llvm-test testsuite and for compiling C/C++ programs. Note that you can optionally
location must be specified when the LLVM suite is configured.</p> <a href="CFEBuildInstrs.html">build llvm-gcc yourself</a> after building the
main LLVM repository.</p>
<p>To install the GCC front end, do the following:</p> <p>To install the GCC front end, do the following:</p>
@ -743,6 +744,14 @@ location must be specified when the LLVM suite is configured.</p>
-</tt></li> -</tt></li>
</ol> </ol>
<p>Once the binary is uncompressed, you should add a symlink for llvm-gcc and
llvm-g++ to some directory in your path. When you configure LLVM, it will
automatically detect llvm-gcc's presence (if it is in your path) enabling its
use in llvm-test. Note that you can always build or install llvm-gcc at any
pointer after building the main LLVM repository: just reconfigure llvm and
llvm-test will pick it up.
</p>
<p>The binary versions of the GCC front end may not suit all of your needs. For <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 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 file, not "fix" a header file that needs to be fixed for GCC, or it may be