[llvm-commits] CVS: llvm/docs/CFEBuildInstrs.html FAQ.html GettingStarted.html TestingGuide.html
Reid Spencer
reid at x10sys.com
Tue Dec 14 14:07:40 PST 2004
Changes in directory llvm/docs:
CFEBuildInstrs.html updated: 1.33 -> 1.34
FAQ.html updated: 1.26 -> 1.27
GettingStarted.html updated: 1.93 -> 1.94
TestingGuide.html updated: 1.21 -> 1.22
---
Log message:
Correct documentation to reflect the change in location of the CFE runtime
libraries. They are now in $CFEINSTALL/lib not $CFEINSTALL/bytecode-lib.
---
Diffs of the changes: (+15 -15)
Index: llvm/docs/CFEBuildInstrs.html
diff -u llvm/docs/CFEBuildInstrs.html:1.33 llvm/docs/CFEBuildInstrs.html:1.34
--- llvm/docs/CFEBuildInstrs.html:1.33 Fri Dec 10 09:47:17 2004
+++ llvm/docs/CFEBuildInstrs.html Tue Dec 14 16:07:29 2004
@@ -231,9 +231,9 @@
These are the commands you need.</p>
<pre>
% gmake
- % mkdir $CFEINSTALL/bytecode-libs
+ % mkdir $CFEINSTALL/lib
% gmake -C runtime install-bytecode
- % setenv LLVM_LIB_SEARCH_PATH $CFEINSTALL/bytecode-libs
+ % setenv LLVM_LIB_SEARCH_PATH $CFEINSTALL/lib
</pre></li>
<li><p>Optionally, build a symbol table for the newly installed runtime
@@ -332,7 +332,7 @@
Brian Gaeke<br>
<a href="http://llvm.cs.uiuc.edu">LLVM Compiler Infrastructure</a><br>
- Last modified: $Date: 2004/12/10 15:47:17 $
+ Last modified: $Date: 2004/12/14 22:07:29 $
</address>
</body>
Index: llvm/docs/FAQ.html
diff -u llvm/docs/FAQ.html:1.26 llvm/docs/FAQ.html:1.27
--- llvm/docs/FAQ.html:1.26 Wed Dec 8 12:01:27 2004
+++ llvm/docs/FAQ.html Tue Dec 14 16:07:29 2004
@@ -364,10 +364,10 @@
To fix it, verify that LLVM_LIB_SEARCH_PATH points to the correct directory
and that libcrtend.a is inside. For pre-built LLVM GCC front ends, this
should be the absolute path to
-<tt>cfrontend/<<i>platform</i>>/llvm-gcc/bytecode-libs</tt>. If you've
+<tt>cfrontend/<<i>platform</i>>/llvm-gcc/lib</tt>. If you've
built your own LLVM GCC front end, then ensure that you've built and installed
the libraries in <tt>llvm/runtime</tt> and have LLVM_LIB_SEARCH_PATH pointing
-to the <tt>LLVMGCCDIR/bytecode-libs</tt> subdirectory.
+to the <tt>$LLVMGCCDIR/lib</tt> subdirectory.
</p>
</div>
@@ -460,7 +460,7 @@
<p>
In order to find libcrtend.a, you must have the directory in which it lives in
your LLVM_LIB_SEARCH_PATH environment variable. For the binary distribution of
-the LLVM GCC front end, this will be the full path of the bytecode-libs
+the LLVM GCC front end, this will be the full path of the <tt>lib</tt>
directory inside of the LLVM GCC distribution.
</p>
</div>
@@ -554,7 +554,7 @@
src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"></a>
<a href="http://llvm.cs.uiuc.edu">LLVM Compiler Infrastructure</a><br>
- Last modified: $Date: 2004/12/08 18:01:27 $
+ Last modified: $Date: 2004/12/14 22:07:29 $
</address>
</body>
Index: llvm/docs/GettingStarted.html
diff -u llvm/docs/GettingStarted.html:1.93 llvm/docs/GettingStarted.html:1.94
--- llvm/docs/GettingStarted.html:1.93 Fri Dec 10 09:47:17 2004
+++ llvm/docs/GettingStarted.html Tue Dec 14 16:07:29 2004
@@ -548,7 +548,7 @@
<tt>.cshrc</tt> or <tt>.profile</tt>.
<dl>
- <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt><i>LLVMGCCDIR</i>/bytecode-libs</tt>
+ <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt><i>LLVMGCCDIR</i>/lib</tt>
<dd>
This environment variable helps the LLVM GCC front end find bytecode
libraries that it will need for compilation.
@@ -806,10 +806,10 @@
<tt>LLVM_LIB_SEARCH_PATH</tt> environment variable in your startup shell
scripts. This environment variable is used to locate "system" libraries like
"<tt>-lc</tt>" and "<tt>-lm</tt>" when linking. This variable should be set to
-the absolute path of the <tt>bytecode-libs</tt> subdirectory of the GCC front
-end, or <i>LLVMGCCDIR</i>/<tt>bytecode-libs</tt>. For example, one might set
+the absolute path of the <tt>lib</tt> subdirectory of the GCC front
+end, or <i>LLVMGCCDIR</i>/<tt>lib</tt>. For example, one might set
<tt>LLVM_LIB_SEARCH_PATH</tt> to
-<tt>/home/vadve/lattner/local/x86/llvm-gcc/bytecode-libs</tt> for the x86
+<tt>/home/vadve/lattner/local/x86/llvm-gcc/lib</tt> for the x86
version of the GCC front end on our research machines.</p>
</div>
@@ -1503,7 +1503,7 @@
<a href="mailto:sabre at nondot.org">Chris Lattner</a><br>
<a href="http://llvm.x10sys.com/rspencer/">Reid Spencer</a><br>
<a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
- Last modified: $Date: 2004/12/10 15:47:17 $
+ Last modified: $Date: 2004/12/14 22:07:29 $
</address>
</body>
</html>
Index: llvm/docs/TestingGuide.html
diff -u llvm/docs/TestingGuide.html:1.21 llvm/docs/TestingGuide.html:1.22
--- llvm/docs/TestingGuide.html:1.21 Fri Dec 10 09:47:17 2004
+++ llvm/docs/TestingGuide.html Tue Dec 14 16:07:29 2004
@@ -474,7 +474,7 @@
</p>
<pre>
-5 3 * * * LLVM_LIB_SEARCH_PATH=.../llvm-gcc/bytecode-libs $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan ...CVSREPOSTRING... $HOME/buildtest-X86 $HOME/cvs/testresults-X86
+5 3 * * * LLVM_LIB_SEARCH_PATH=.../llvm-gcc/lib $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan ...CVSREPOSTRING... $HOME/buildtest-X86 $HOME/cvs/testresults-X86
</pre>
<p>Or, you can create a shell script to encapsulate the running of the script.
@@ -488,7 +488,7 @@
export LLVMGCCDIR=/proj/work/llvm/cfrontend/install
export PATH=/proj/install/bin:$LLVMGCCDIR/bin:$PATH
export LD_LIBRARY_PATH=/proj/install/lib
-export LLVM_LIB_SEARCH_PATH=/proj/work/llvm/cfrontend/install/bytecode-libs
+export LLVM_LIB_SEARCH_PATH=/proj/work/llvm/cfrontend/install/lib
cd $BASE
cp /proj/work/llvm/llvm/utils/NightlyTest.pl .
nice ./NightlyTest.pl -nice -release -verbose -parallel -enable-linscan -noexternals
@@ -513,7 +513,7 @@
John T. Criswell<br>
<a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br/>
- Last modified: $Date: 2004/12/10 15:47:17 $
+ Last modified: $Date: 2004/12/14 22:07:29 $
</address>
</body>
</html>
More information about the llvm-commits
mailing list