Add info about the LLVM_LIB_SEARCH_PATH envvar

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@6096 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html
index 7d997c9565a239538890c91d66fe9c6f3eb4a6e1..d7d47aefadc4821044a4705b129d8566ab8f49b7 100644 (file)
--- a/docs/GettingStarted.html
+++ b/docs/GettingStarted.html
@@ -80,6 +80,7 @@
     <li>Edit <tt>Makefile.config</tt> to set local paths.  This includes
         setting the install location of the C frontend, and the various paths
         to the C and C++ compilers used to build LLVM itself.
+    <li>Set your LLVM_LIB_SEARCH_PATH environment variable.
     <li><tt>gmake -k |& tee gnumake.out
            &nbsp;&nbsp;&nbsp;# this is csh or tcsh syntax</tt>
     </ol>
@@ -145,6 +146,15 @@
     <p><li><i>PURIFY</i>       = Path to the purify program.
     </ul>
 
+    In addition to settings in this file, you must set a
+    <tt>LLVM_LIB_SEARCH_PATH</tt> environment variable in your startup 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 for the bytecode-libs subdirectory of the C front-end
+    install.  For example,
+    <tt>/home/vadve/lattner/local/x86/llvm-gcc/bytecode-libs</tt> for the X86
+    version of the C front-end, on our research machines.<p>
+
     <!------------------------------------------------------------------------->
     <h3><a name="objfiles">The location for LLVM object files</a></h3>
     <!------------------------------------------------------------------------->
@@ -462,7 +472,7 @@
 
            <!-- Created: Mon Jul  1 02:29:02 CDT 2002 -->
            <!-- hhmts start -->
-Last modified: Thu Feb 13 22:20:39 CST 2003
+Last modified: Sun May 11 16:49:46 CDT 2003
 <!-- hhmts end -->
   </body>
 </html>