From: Reid Spencer
Date: Wed, 22 Dec 2004 06:29:07 +0000 (+0000)
Subject: For PR432:
X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=d4694f9cf573ad68bc31dfe3d1fdca20d42fce28;p=oota-llvm.git
For PR432:
* llvmgcc -> llvm-gcc
* llvmg++ -> llvm-g++
* remove references to --with-llvmgccdir configure option
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@19098 91177308-0d34-0410-b5e6-96231b3b80d8
---
diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html
index cb81b19c3f8..f3c805c7f0e 100644
--- a/docs/GettingStarted.html
+++ b/docs/GettingStarted.html
@@ -113,10 +113,12 @@ and performance.
Remember that you were warned twice about reading the documentation.
Install the GCC front end:
- - cd where-you-want-the-C-front-end-to-live
+
- cd where-you-want-the-C-front-end-to-live
- gunzip --stdout cfrontend.platform.tar.gz | tar -xvf -
+
- cd cfrontend/platform
- ./fixheaders
+ ./fixheaders
+ - Add the cfrontend's "bin" directory to your PATH variable
Get the Source Code
@@ -173,9 +175,9 @@ and performance.
files and run configure to configure the Makefiles and
header files for the default platform. Useful options include:
- - --with-llvmgccdir=directory
-
Specify the full pathname of where the LLVM GCC frontend is
- installed.
+ - --prefix=directory
+
Specify for directory the full pathname of where you
+ want the LLVM tools and libraries to be installed.
- --enable-spec2000=directory
Enable the SPEC2000 benchmarks for testing. The SPEC2000
benchmarks should be available in
@@ -552,11 +554,11 @@ You can set these on the command line, or better yet, set them in your
of your bytecode libraries. It is optional and provided only a convenience
since you can specify the paths using the -L options of the tools.
-
- alias llvmgcc LLVMGCCDIR/bin/gcc
- - alias llvmg++ LLVMGCCDIR/bin/g++
+ - alias llvmgcc='llvm-gcc'
+ - alias llvmg++='llvm-g++'
- These aliases allow you to use the LLVM C and C++ front ends
- without putting them in your PATH or typing in their complete
- pathnames.
+ under alternative names. It is assumed that llvm-gcc and llvm-g++ are
+ in your path. The LLVM makefiles will use llvm-gcc and llvm-g++ directly.
@@ -749,13 +751,6 @@ script to configure the build system:
The following options can be used to set or enable LLVM specific options:
- - --with-llvmgccdir=LLVMGCCDIR
- -
- Path to the location where the LLVM GCC front end binaries and
- associated libraries were installed. This must be specified as an
- absolute pathname.
-
-
- --with-tclinclude
- Path to the tcl include directory under which the tclsh can be
found. Use this if you have multiple tcl installations on your machine and you
@@ -1251,21 +1246,21 @@ information is in the Command Guide.
translates LLVM bytecode to a SPARC or x86 assembly file, or to C code (with
the -march=c option).
- - llvmgcc
- - llvmgcc is a GCC-based C frontend
+
- llvm-gcc
+ - llvm-gcc is a GCC-based C frontend
that has been retargeted to emit LLVM code as the machine code output. It
works just like any other GCC compiler, taking the typical -c, -S, -E,
-o options that are typically used. The source code for the
- llvmgcc tool is currently not included in the LLVM CVS tree
+ llvm-gcc tool is currently not included in the LLVM CVS tree
because it is quite large and not very interesting.
- gccas
- - This tool is invoked by the llvmgcc frontend as the
+
- This tool is invoked by the llvm-gcc frontend as the
"assembler" part of the compiler. This tool actually assembles LLVM
assembly to LLVM bytecode, performs a variety of optimizations, and
outputs LLVM bytecode. Thus when you invoke
- llvmgcc -c x.c -o x.o, you are causing gccas to be
+ llvm-gcc -c x.c -o x.o, you are causing gccas to be
run, which writes the x.o file (which is an LLVM bytecode file
that can be disassembled or manipulated just like any other bytecode
file). The command line interface to gccas is designed to be
@@ -1397,7 +1392,7 @@ are code generators for parts of LLVM infrastructure.
Next, compile the C file into a LLVM bytecode file:
- % llvmgcc hello.c -o hello
+ % llvm-gcc hello.c -o hello
Note that you should have already built the tools and they have to be
in your path, at least gccas and gccld.