projects
/
oota-llvm.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
952e38c
)
Mention a note about having gccas and gccld in the path when running llvm-gcc.
author
Misha Brukman
<brukman+llvm@gmail.com>
Tue, 22 Jun 2004 18:48:58 +0000
(18:48 +0000)
committer
Misha Brukman
<brukman+llvm@gmail.com>
Tue, 22 Jun 2004 18:48:58 +0000
(18:48 +0000)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@14328
91177308
-0d34-0410-b5e6-
96231b3b80d8
docs/GettingStarted.html
patch
|
blob
|
history
diff --git
a/docs/GettingStarted.html
b/docs/GettingStarted.html
index 69c3603f1fe618740d139a77edf4dfdab3e154b9..6b8e2c105c09d5d6e0713517d74d441646f0c8d2 100644
(file)
--- a/
docs/GettingStarted.html
+++ b/
docs/GettingStarted.html
@@
-1136,6
+1136,9
@@
are code generators for parts of LLVM infrastructure.</p>
<li><p>Next, compile the C file into a LLVM bytecode file:</p>
<p><tt>% llvmgcc hello.c -o hello</tt></p>
+ <p>Note that you should have already built the tools and they have to be
+ in your path, at least <tt>gccas</tt> and <tt>gccld</tt>.</p>
+
<p>This will create two result files: <tt>hello</tt> and
<tt>hello.bc</tt>. The <tt>hello.bc</tt> is the LLVM bytecode that
corresponds the the compiled program and the library facilities that it